Skip to content

test: pgmq ownership modification #1536

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

Open
1 of 3 tasks
steve-chavez opened this issue Apr 11, 2025 · 0 comments
Open
1 of 3 tasks

test: pgmq ownership modification #1536

steve-chavez opened this issue Apr 11, 2025 · 0 comments

Comments

@steve-chavez
Copy link
Member

steve-chavez commented Apr 11, 2025

Problem

The change on #1362 modified pgmq db objects default owner, which is supabase_admin, as it's on every extension.

This is not tested and it's not an obvious behavior.

Solution

Test all the db objects owners:

steve-chavez added a commit that referenced this issue Apr 11, 2025
The change on #1362 modified
pgmq functions default owner, which is `supabase_admin`, to `postgres`.

This tests function owners of pgmq.

Partly addresses #1536.
steve-chavez added a commit that referenced this issue Apr 11, 2025
The change on #1362 modified
pgmq functions default owner, which is `supabase_admin`, to `postgres`.

This tests function owners of pgmq.

Partly addresses #1536.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant