Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen
Date
Msg-id 4F8DFA9A.3050005@dunslane.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen  (Andrew Dunstan <andrew@dunslane.net>)
Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers

On 04/17/2012 07:08 PM, Robert Haas wrote:
> On Tue, Apr 17, 2012 at 6:39 PM, Andrew Dunstan<andrew@dunslane.net>  wrote:
>> Don't override arguments set via options with positional arguments.
>>
>> A number of utility programs were rather careless about paremeters
>> that can be set via both an option argument and a positional
>> argument. This leads to results which can violate the Principal
>> Of Least Astonishment. These changes refuse to use positional
>> arguments to override settings that have been made via positional
>> arguments. The changes are backpatched to all live branches.
>>
>> Branch
>> ------
>> REL8_3_STABLE
> Uh, isn't it kind of a bad idea to back-patch something like this?  It
> seems like a behavior change.


It was discussed. I think the previous behaviour is a bug. It can't be 
sane to be allowed to do:
   initdb -D foo bar


cheers

andrew



pgsql-hackers by date:

Previous
From: Christopher Browne
Date:
Subject: Re: Bug tracker tool we need
Next
From: Andrew Dunstan
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen