| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Clover White <mywhiteclover(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: why was the VAR 'optind' never changed in initdb? |
| Date: | 2012-04-09 18:27:38 |
| Message-ID: | 4F832A1A.1020802@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/09/2012 01:38 PM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-04-09 18:29:46 | Re: Regarding column reordering project for GSoc 2012 |
| Previous Message | Robert Haas | 2012-04-09 18:20:10 | Re: bug in fast-path locking |