Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Ron Snyder <snyder(at)roguewave(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)
Date: 2002-09-29 02:37:23
Message-ID: 7136.1033267043@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Can someone tell me where we are on this; exactly what writability do
> we have in 7.3?

The current code implements what I suggested in that note, viz:
default permissions for new databases are
owner = all rights (ie, create schema and create temp)
public = create temp right only
but template1 and template0 are set to
owner (postgres user) = all rights
public = no rights
by initdb.

Also, the "public" schema within template1 is empty but writable by
public. This is annoying, but at least it's easy to fix if you
mess up --- you can DROP SCHEMA public CASCADE and then recreate
the schema. (Or not, if you don't want to.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-09-29 02:41:50 Re: [PATCHES] Cascaded Column Drop
Previous Message Rod Taylor 2002-09-29 02:19:50 Re: [PATCHES] Cascaded Column Drop