Grant Schema Permissions for PostgreSQL 15+ Compatibility #1614
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.
With PostgreSQL 15 and onwards, there has been a change in the way table creation permissions are handled for users. Not directly related to pgAdmin 4, but I think people may run into this.
Normally, after allowing a user to CREATE tables within a database, you didn't have to specifically define that they had the permission to do that within a SCHEMA, since public would be the default one.
With PostgreSQL 15, this has changed source
ERROR: permission denied for schema public
The error occurred during the installation of Alfresco using the ZIP installer with PostgreSQL 17.
To fix this, I added the following two lines to the PostgreSQL configuration: