From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
Cc: Holger Jakobs <holger@jakobs.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Create Read only user
Date: Fri, 22 Jan 2021 19:38:24 -0500
Message-ID: <1280789.1611362304@sss.pgh.pa.us> (raw)
In-Reply-To: <CAOC+FBUmywn6_+E75R3qjs+y=jjpkEP0VKEj9PNaP=YBMw_9Lg@mail.gmail.com>
References: <CALhHtcA5CYQU0SLU673qAdZiixAJJ8GF2ZEJV7YSiq03h5W-jw@mail.gmail.com>
<87bldgbv9r.fsf@gmail.com>
<9e9f3cd6-bd51-29b3-887e-c3af2db91f54@jakobs.com>
<CAOC+FBUmywn6_+E75R3qjs+y=jjpkEP0VKEj9PNaP=YBMw_9Lg@mail.gmail.com>
Wells Oliver <wells.oliver@gmail.com> writes:
> Is there any weird unexpected downside to revoking perms on PUBLIC from all
> my users? It drives me nuts the random stuff that fills this schema up,
> even after I got everyone their own shiny personal schema.
As far as the system is concerned, no; in fact you could drop PUBLIC
altogether if you like. Your users might whine though...
(Actually, dropping it altogether might be a bad idea, because then
it will come back in your next upgrade. I think that if you just
change the permissions on it, modern versions of pg_dump/pg_upgrade
will propagate that successfully.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, wells.oliver@gmail.com, holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: Create Read only user
In-Reply-To: <1280789.1611362304@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox