Re: Rationale for PUBLIC having CREATE and USAGE privileges on the schema "public" by default

Okay, thanks, I'll stop worrying about the defaults then. Have a nice evening! Olegs On Sat, Feb 17, 2018 at 11:49 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > On Saturday, February 17, 2018, Olegs Jeremejevs > wrote: > >> Okay, in other words, th

Re: Rationale for PUBLIC having CREATE and USAGE privileges on the schema "public" by default

david.g.johns...@gmail.com> wrote: > On Saturday, February 17, 2018, Olegs Jeremejevs > wrote: > >> Thanks for the reply. >> >> > I'm not sure whether you are really being limited/forced here or if >> you are thinking that having CREATE and USAGE on a s

Re: Rationale for PUBLIC having CREATE and USAGE privileges on the schema "public" by default

revoked or the schema isn't deleted, so I take back the "essentially forced to" part. Regards, Olegs On Sat, Feb 17, 2018 at 2:57 AM, David G. Johnston < david.g.johns...@gmail.com> wrote: > On Fri, Feb 16, 2018 at 4:50 PM, Olegs Jeremejevs > wrote: > >&g

Rationale for PUBLIC having CREATE and USAGE privileges on the schema "public" by default

Hi, I'm aware that these default privileges are documented: https://www.postgresql.org/docs/10/static/ddl-schemas.html#DDL-SCHEMAS-PRIV However, I'm unable to find any reasoning behind their existence. Normally, one can just revoke them and move on, but they have caused me some trouble in a mana