Re: Default privileges for new databases (was Re: Can't - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Default privileges for new databases (was Re: Can't
Date
Msg-id 200206172143.g5HLhbn15614@candle.pha.pa.us
Whole thread Raw
In response to Re: Default privileges for new databases (was Re: Can't  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut wrote:
> Josh Berkus writes:
> 
> > Yes.  I think there should be a not optional INITDB switch:  either --secure
> > or --permissive.   People usually know at the time of installation whether
> > they're building a web server (secure) or a home workstation (permissive).
> 
> If you're on a home workstation you make yourself a superuser and be done
> with it.
> 
> Adding too many options to initdb is not a path I would prefer since
> initdb happens mostly hidden from the user these days.

Well, we have the config files for most things.  I would just like to
have an easy way to configure things that aren't GUC parameters.  That's
where the initdb idea came from.  Other ideas?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Roadmap for a Win32 port
Next
From: Hiroshi Inoue
Date:
Subject: Re: SetQuerySnapshot, once again