Re: xpath changes in the recent back branches - Mailing list pgsql-hackers

From Robert Haas
Subject Re: xpath changes in the recent back branches
Date
Msg-id CA+TgmoZ4nebSTidiCi=_LhUh4HgjpfAhpmwpJEMtcBavWNMxPA@mail.gmail.com
Whole thread Raw
In response to Re: xpath changes in the recent back branches  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: xpath changes in the recent back branches
List pgsql-hackers
On Wed, Mar 4, 2015 at 4:11 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> That said, if I understand your test case correctly, this would
> basically be an argument against any semantic corrections in stable
> releases, since user code could expect to continue to work with the
> previous incorrect value.
>
> You can always test the server version number, and you'll have to for
> the next major release anyway.

That's not really the problem, of course.  The problem is you upgrade
and your app unexpectedly breaks.  The complexity of fixing that once
it's happened is not entirely irrelevant, but it's not really the main
problem, either.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: MD5 authentication needs help
Next
From: Alvaro Herrera
Date:
Subject: Re: Idea: closing the loop for "pg_ctl reload"