| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: xpath changes in the recent back branches |
| Date: | 2015-03-04 22:00:20 |
| Message-ID: | CA+TgmoZ4nebSTidiCi=_LhUh4HgjpfAhpmwpJEMtcBavWNMxPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 4, 2015 at 4:11 PM, Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-03-04 22:04:02 | Re: Idea: closing the loop for "pg_ctl reload" |
| Previous Message | Robert Haas | 2015-03-04 21:56:53 | Re: MD5 authentication needs help |