Skip site navigation (1) Skip section navigation (2)

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen
Date: 2012-04-18 03:22:56
Message-ID: CA+TgmoYnxFcGnsQeVJwiiDeViU2sqs4ohRbTD7m4mag7d-W6ZQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Tue, Apr 17, 2012 at 10:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I can see both sides of this.  I agree that the old behavior is buggy,
> but what I imagine Robert is worried about is scripts that accidentally
> work okay today and would stop working once the PG programs are fixed
> to complain about bogus usage.  People tend not to like it if you make
> that kind of change in a minor release.

Exactly.

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

In response to

pgsql-hackers by date

Next:From: Greg SmithDate: 2012-04-18 03:23:00
Subject: Re: Bug tracker tool we need
Previous:From: Robert HaasDate: 2012-04-18 03:22:07
Subject: Re: Bug tracker tool we need

pgsql-committers by date

Next:From: Peter EisentrautDate: 2012-04-18 09:46:45
Subject: Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen
Previous:From: Tom LaneDate: 2012-04-18 02:53:44
Subject: Re: Re: [COMMITTERS] pgsql: Don't override arguments set via options with positional argumen

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group