Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postgres CDC: upstream table in different schema will sync into same Table #17890

Closed
StrikeW opened this issue Aug 1, 2024 · 3 comments · Fixed by #18868
Closed

Postgres CDC: upstream table in different schema will sync into same Table #17890

StrikeW opened this issue Aug 1, 2024 · 3 comments · Fixed by #18868
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@StrikeW
Copy link
Contributor

StrikeW commented Aug 1, 2024

Describe the bug

There are two tables named t2 in different schema, both of them will be synced into the same RW table created via sql:
create table t2a (...) from pg_source table 'public.t2'. This is unexpected, since t2a only need data from public.t2.

mydb=#  select * from pg_publication_tables;
    pubname     | schemaname | tablename
----------------+------------+-----------
 rw_publication | abs        | t2
 rw_publication | public     | t2
(4 rows)

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

v1.9.2

Additional context

No response

@StrikeW StrikeW added the type/bug Something isn't working label Aug 1, 2024
@StrikeW StrikeW self-assigned this Aug 1, 2024
@github-actions github-actions bot added this to the release-1.11 milestone Aug 1, 2024
@StrikeW StrikeW changed the title PG CDC: upstream table in different schema will sync into same Table Postgres CDC: upstream table in different schema will sync into same Table Aug 1, 2024
Copy link
Contributor

github-actions bot commented Oct 1, 2024

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄

@hzxa21
Copy link
Collaborator

hzxa21 commented Oct 8, 2024

@StrikeW Is this issue fixed?

@StrikeW
Copy link
Contributor Author

StrikeW commented Oct 9, 2024

@StrikeW Is this issue fixed?

No yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants