Fix deployment with PostgreSQL 15 #75
Conversation
We previously did not change the database owner for PostgreSQL, resulting in the database being owned by the `postgres` user. PostgreSQL 15 revoked the CREATE permission from all users except a database owner from the public schema. As a consequence, migration that are expected to create objects are not allowed to do so with this version and newer of PostgreSQL. Explicitly make the database user the owner of it, to allow migrations.
|
@opus-codium/core I am not sure if we should consider this a |
I made my mind: this previously worked because older version of PostgreSQL allowed any user to create objects in the public schema of a database. This was realistically a bug that was fixed upstream, and due to the fact that we did not set a proper owner on the database, it beats us today. |
Its a fix to me: we manage whole application and its a side effect of postgresql upgrade, not due to our module. |
We previously did not change the database owner for PostgreSQL,
resulting in the database being owned by the
postgresuser.PostgreSQL 15 revoked the CREATE permission from all users except a
database owner from the public schema. As a consequence, migration that
are expected to create objects are not allowed to do so with this
version and newer of PostgreSQL.
Explicitly make the database user the owner of it, to allow migrations.
Also include: