Re: Adding a --quiet option to initdb

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> This warning was added because of security considerations AFAIR.  If the
> intent is to make initdb super-quiet, we still have to have security in
> mind.  So if you want it to not say anything by default, instead of
> throwing a warning it should throw an error and refuse to continue;
> unless a default password is specified or a --silently-enable-trust-auth
> switch is passed, in either of which cases it can silently continue.

There is 0 chance that we will design initdb to fail by default.
        regards, tom lane