On 04/17/2012 07:08 PM, Robert Haas wrote:
> On Tue, Apr 17, 2012 at 6:39 PM, Andrew Dunstan<andrew(at)dunslane(dot)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

In response to

• Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen at 2012-04-17 23:08:01 from Robert Haas

Responses

• Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen at 2012-04-17 23:38:34 from Andrew Dunstan
• Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen at 2012-04-18 09:46:45 from Peter Eisentraut

pgsql-hackers by date

Next:	From: Andrew Dunstan	Date: 2012-04-17 23:38:34
	Subject: Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen
Previous:	From: Christopher Browne	Date: 2012-04-17 23:08:59
	Subject: Re: Bug tracker tool we need

pgsql-committers by date

Next:	From: Andrew Dunstan	Date: 2012-04-17 23:38:34
	Subject: Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen
Previous:	From: Robert Haas	Date: 2012-04-17 23:08:01
	Subject: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen