Re: xpath changes in the recent back branches

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Marko Tiikkaja <marko(at)joh(dot)to>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: xpath changes in the recent back branches
Date: 2015-03-04 16:26:57
Message-ID: 17500.1425486417@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Feb 19, 2015 at 5:53 AM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
>> I'm not sure how changing behavior like this in a minor release was
>> considered acceptable.

> I'm guessing that the fact that it changes behavior in cases like this
> wasn't recognized, but I suppose Peter will have to be the one to
> comment on that.

It was considered to be a bug fix; more, given the few complaints about
the clearly-broken old behavior, we thought it was a fix that would affect
few people, and them positively. Sorry you're not happy about it, but
these things are always judgment calls.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2015-03-04 16:28:20 Re: pg_upgrade and rsync
Previous Message Robert Haas 2015-03-04 16:26:22 Re: failures with tuplesort and ordered set aggregates (due to 5cefbf5a6c44)