Default privileged user for PG 15 connection pool
Because of a change in Postgresql v15, user's no longer have access to the public schema by default. This means they can no longer create/modify objects by default. This is a breaking change because before you could create database pool for a specific user/db combo and expect that they would be able to access the objects in that database. I believe that Aiven should automatically grant permissions for a particular user on a particular database when there is a pool made for that user/db combo
AdminJorge Uribe
(Senior Support Engineer, Aiven.io)
shared this idea
PostgreSQL 15 removes the global write privilege from the public schema. However, it is possible to provide the same level of collaboration to users, by making use of user schemas, and role-based access. Continuing the pre-PostgreSQL 15 practices on PostgreSQL 15 is discouraged.