You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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. 😄
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, sincet2a
only need data frompublic.t2
.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
The text was updated successfully, but these errors were encountered: