| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ron Snyder <snyder(at)roguewave(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Default privileges for new databases (was Re: Can't |
| Date: | 2002-06-17 21:43:37 |
| Message-ID: | 200206172143.g5HLhbn15614@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-06-17 21:44:46 | Re: [Fwd: contrib/showguc (was Re: [HACKERS] revised sample |
| Previous Message | Bruce Momjian | 2002-06-17 21:31:01 | Re: Roadmap for a Win32 port |