| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
| Cc: | Holger Jakobs <holger(at)jakobs(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Create Read only user |
| Date: | 2021-01-23 00:38:24 |
| Message-ID: | 1280789.1611362304@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Wells Oliver <wells(dot)oliver(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mr Doss | 2021-01-25 10:36:06 | You're invited to share this calendar |
| Previous Message | Ron | 2021-01-23 00:26:31 | Re: Create Read only user |