Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
First try with role reset #427
First try with role reset #427
Changes from 3 commits
92e428c
401f355
089b8fd
3692d3d
41acb0b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we
ALTER ROLE sharding_user ROLE TO <new role>
to simulate the same error we saw in production?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious about the error, if you're willing to share. I'm not too familiar with
RESET USER
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@levkk we had 2 users in the DB, lets call them
A
andB
.We had run
ALTER ROLE A SET ROLE B
, which has the effect of runningSET ROLE B
after you open a connection with usernameA
. We had configuredpgbouncer
andpgcat
to both connect with usernameA
.When we run
create table
on pgbouncer, it was owned byB
due to this config.When we run
create table
on pgcat, a previous query had runDISCARD ALL
in the pgcat server connection, and then the table was owned byA
. We found that we could runRESET ROLE
to fix it back toSET ROLE b
after aDISCARD ALL
was run.Our permissions were all configured with assuming
B
owns the tables, so when we started creating tables withA
as the owner after switching to pgcat, we had some errors.