On Mon, Nov 2, 2020 at 01:41:09PM -0500, Stephen Frost wrote: > At least from seeing the users that start out with PG and then come to > the Slack or IRC channel asking questions, the on-boarding experience > today typically consists of 'apt install postgresql' and then complaints > that they aren't able to figure out how to log into PG (often asking > about what the default password is to log in as 'postgres', or why the > system is saying 'role "root" does not exist'). Once a user gets to the > point of understanding or wanting to create other roles in the system, > saying they need to create a schema for that role if they want it to be > able to create objects (just like a user needing a home directory) > doesn't seem likely to be all that unexpected.
It is a good point that the user has to create another user before this becomes a usability issue. It seems at the time the first user is created (non-postgres), the admin needs to decide how the public schema should behave. -- Bruce Momjian <br...@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
