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

2002-09-28 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > How did you get temp schemas non-world writable in template1 but not in > the databases, or am I confused? That right is associated with the database, so we just have to control what CREATE DATABASE puts in the new pg_database row.

Re: Default privileges for new databases (was Re: [HACKERS] Can't import

2002-09-28 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> 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

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

2002-09-28 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> 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 t

Re: Default privileges for new databases (was Re: [HACKERS] Can't import

2002-09-28 Thread Bruce Momjian
Can someone tell me where we are on this; exactly what writability do we have in 7.3? --- Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Have we addressed this? I don't think so. > > No, it's not done ye

Re: Default privileges for new databases (was Re: [HACKERS] Can't import

2002-09-01 Thread Bruce Momjian
OK, we are rolling out schemas in 7.3. We better figure out if we have the best solution for this. --- Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Have we addressed this? I don't think so. > > No, it'

Re: Default privileges for new databases (was Re: [HACKERS] Can't import

2002-08-26 Thread Bruce Momjian
Sorry, I am confused. Why can we modify temp's permissions on CREATE DATABASE but not public's permissions? --- Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Have we addressed this? I don't think so. >

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

2002-08-26 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Have we addressed this? I don't think so. No, it's not done yet. My inclination is * Template1 has temp table creation and schema creation disabled (disallowed to world) by default. * CREATE DATABASE sets up new databases with temp table creation al

Re: Default privileges for new databases (was Re: [HACKERS] Can't import

2002-08-26 Thread Bruce Momjian
Have we addressed this? I don't think so. --- Tom Lane wrote: > Ron Snyder <[EMAIL PROTECTED]> writes: > > May 31 16:11:50 vault pgcvs[2135]: [91] LOG: query: Create Temporary Table > > pg_dump_blob_xref(oldOid pg_catalog

Re: Default privileges for new databases (was Re: [HACKERS] Can't import

2002-06-13 Thread Bruce Momjian
Josh Berkus wrote: > > Tom, > > > Probably we should have temp table creation allowed to all by default. > > I'm not convinced that that's a good idea for schema-creation privilege > > though. Related issues: what should initdb set as the permissions for > > template1? Would it make sense for

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

2002-06-10 Thread Josh Berkus
Tom, > Probably we should have temp table creation allowed to all by default. > I'm not convinced that that's a good idea for schema-creation privilege > though. Related issues: what should initdb set as the permissions for > template1? Would it make sense for newly created databases to copy >