It has probably be said before, but new users need
to be able to get up and running on their *development*
system quickly. Throwing new users for a loop with
the password configuration issues would be a problem.
Most people would put up a test server first anyway
in order to check things out and configure as necessary.
--elein
On Mon, Jul 12, 2004 at 05:27:23PM -0400, Tom Lane wrote:
> "Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
> > IMO, forcing su password at initdb time (allowing blank password with a
> > very stern warning) and bumping localhost to auth is the right way to
> > go.
>
> This isn't happening for a number of reasons, the most obvious being
> that we cannot require initdb to be run interactively. (That stern
> warning will not impress /dev/null.)
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
