[MM3-users] Re: Error -- postorius Un-handled exception

On Sat, Jan 27, 2024 at 8:17 AM Mark <imark@posteo.net> wrote:

...

3. For the user "mailman" to access the databases I needed to change the owner to mailman (even though all privileges has been granted) ...

On 2024-01-27 18:51, Odhiambo Washington wrote:

The issue you're dealing with in that case is this change in PostgreSQL-15 discussed in this blog: https://www.cybertec-postgresql.com/en/error-permission-denied-schema-public...

I have never needed to do psql -d mailman -U mailman -W. I used the steps documented above to enable mailman user to write to the database.

postgres=# \c mailmanweb postgres You are now connected to database "mailmanweb" as user "postgres". mailmanweb=# GRANT ALL ON SCHEMA public TO mailman; GRANT mailmanweb=# \c mailman postgres You are now connected to database "mailman" as user "postgres". mailmanweb=# GRANT ALL ON SCHEMA public TO mailman; GRANT

TBH, I am not sure which method is the best although I think this option is :)

Thanks for the heads up on that blog Odhiambo.

Agreed. it is a better way of doing it.

--- SNIP --- In PostgreSQL 14 and in prior versions, by default anybody can create a table. The new table will simply end up in the PUBLIC schema. The problem with this approach is that the public schema can quickly turn into a trash can containing all kinds of used and unused tables – which is neither desirable nor recommended. An even bigger problem is security: almost any privilege escalation attack on a PostgreSQL database requires the attacker to create malicious objects. ... The public schema is the perfect vector for such a privilege escalation attack. Therefore PostgreSQL has made a major leap forward and changed this behavior. In version 15, only the database owner can create objects in the public schema.