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