From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(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 |
Date: | 2002-09-29 02:47:42 |
Message-ID: | 200209290247.g8T2lgC11785@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> 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.)
OK, yes, this is what I thought, that public in all databases is
world-writable, but you can control that by dropping and recreating the
public schema, or altering the schema, right?
How did you get temp schemas non-world writable in template1 but not in
the databases, or am I confused?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-09-29 02:50:32 | Re: [PATCHES] Cascaded Column Drop |
Previous Message | Tom Lane | 2002-09-29 02:41:50 | Re: [PATCHES] Cascaded Column Drop |