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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

• pgsql: Don't override arguments set via options with positionalargumen at 2012-04-17 22:39:10 from Andrew Dunstan

Responses

• Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen at 2012-04-17 23:19:54 from Andrew Dunstan

pgsql-hackers by date

Next:	From: Christopher Browne	Date: 2012-04-17 23:08:59
	Subject: Re: Bug tracker tool we need
Previous:	From: Andrew Dunstan	Date: 2012-04-17 22:39:10
	Subject: pgsql: Don't override arguments set via options with positionalargumen

pgsql-committers by date

Next:	From: Andrew Dunstan	Date: 2012-04-17 23:19:54
	Subject: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen
Previous:	From: Andrew Dunstan	Date: 2012-04-17 22:39:10
	Subject: pgsql: Don't override arguments set via options with positionalargumen