| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | 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:20:24 |
| Message-ID: | Pine.LNX.4.44.0206172005110.943-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-06-17 21:21:14 | Re: KSQO parameter |
| Previous Message | Peter Eisentraut | 2002-06-17 21:19:48 | Re: Default privileges for new databases (was Re: Can't |