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

From Peter Eisentraut
Subject Re: Default privileges for new databases (was Re: Can't
Date
Msg-id Pine.LNX.4.44.0206172005110.943-100000@localhost.localdomain
Whole thread Raw
In response to Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Default privileges for new databases (was Re: Can't  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)  (Josh Berkus <josh@agliodbs.com>)
List 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@gmx.net



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Roadmap for a Win32 port
Next
From: Peter Eisentraut
Date:
Subject: Re: KSQO parameter