From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen |
Date: | 2012-04-17 23:19:54 |
Message-ID: | 4F8DFA9A.3050005@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2012-04-17 23:38:34 | Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen |
Previous Message | Robert Haas | 2012-04-17 23:08:01 | Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2012-04-17 23:38:34 | Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen |
Previous Message | Christopher Browne | 2012-04-17 23:08:59 | Re: Bug tracker tool we need |