On 04/09/2012 01:38 PM, Tom Lane wrote:
Andrew Dunstan<and...@dunslane.net> writes:
i.e. we'd forbid:
initdb -D foo bar
which the OP's error more or less devolves to.
Makes sense. Don't we have a similar issue with psql, pg_dump, etc?
From a quick survey:
psql won't override a dbname or username set explicitly with an option
argument.
pg_dump doesn't have an option argument to set the dbname.
pg_restore doesn't have an option argument to set the input file name.
vacuumdb, clusterdb, reindexdb, createlang and droplang all need
remediation. createuser and dropuser look ok.
pg_ctl seems a mess :-( I'll need to look at it closer.
cheers
andrew
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
