"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
