8000 supabase cdc is broken · Issue #20113 · risingwavelabs/risingwave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

supabase cdc is broken #20113

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.

Sign up for GitHub

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

Jump to bottom
Open
pkit opened this issue Jan 12, 2025 · 1 comment
Open

supabase cdc is broken #20113

pkit opened this issue Jan 12, 2025 · 1 comment
Assignees
@wcy-fdu
Labels
type/bug Type: Bug. Only for issues.
Milestone
release-2.5

Comments

@pkit
Copy link
pkit commented Jan 12, 2025

Describe the bug

Supabase CDC is currently unusable

  • IPV6 resolver is not supported
  • IPV4 connection fails because of a sloppy permission check

Error message/log

INVALID_ARGUMENT: Postgres user must have select privilege on table 'public.test1' (SQLSTATE XX000)

To Reproduce

IPV6 connection

CREATE SOURCE IF NOT EXISTS supabase_test WITH (
   connector='postgres-cdc',
   hostname='db.blablabla.supabase.co',
   port='5432',
   username='postgres',
   password='*********',
   database.name='postgres',
   slot.name='test_slot',
   publication.name='test_pub'
);

Fails with:

Internal error: The connection attempt failed. (SQLSTATE XX000)

because IPV6-only DNS resolve is needed.

IPV4 connection

CREATE SOURCE IF NOT EXISTS supabase_test WITH (
   connector='postgres-cdc',
   hostname='aws-0-us-east-2.pooler.supabase.com',
   port='5432',
   username='postgres.blablaba',
   password='********',
   database.name='postgres',
   slot.name='test_slot',
   publication.name='test_pub'
);

Fails with:

INVALID_ARGUMENT: Postgres user must have select privilege on table 'public.test1' (SQLSTATE XX000)

because it uses the username from the connector instead of current_user

Expected behavior

Should work

How did you deploy RisingWave?

it's a cloud version

The version of RisingWave

cloud

Additional context

No response
@pkit pkit added the type/bug Type: Bug. Only for issues. label Jan 12, 2025
@github-actions github-actions bot added this to the release-2.3 milestone Jan 12, 2025
@hzxa21
Copy link
Collaborator
hzxa21 commented May 20, 2025

The version of RisingWave
cloud

Which cloud version are you using? You can see it via select version();

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wcy-fdu wcy-fdu

Labels
type/bug Type: Bug. Only for issues.
Projects
None yet
Milestone
release-2.5
Development

No branches or pull requests
3 participants
@pkit @hzxa21 @wcy-fdu
0