-
Notifications
You must be signed in to change notification settings - Fork 56
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
Add README on adding new read-only accounts to PostgreSQL #79
Comments
Unfortunately, the instructions we used (and provided in the PR) are not sufficiently strict, and allow creating new tables, inserting values there, creating new materialized views etc. Thanks @telezhnaya for reporting it. @telezhnaya May I ask you to find the right set of incantations to achieve the true read-only mode? 😄 I have seen a few places where it is explained that even a new user with no permission granted has access to the
|
That's true. That's why it's better to use non-default schema for the project. Ideally, we need to invoke this command from admin account: My commit was tested it only in the sandbox. I need another account (with more permissions) to test it in real DB. |
To sum up:
In my opinion, it should not be a part of migration |
@frol I deployed these changes to mainnet and testnet |
No description provided.
The text was updated successfully, but these errors were encountered: