On Wed, Mar 4, 2015 at 4:11 PM, Peter Eisentraut <pete...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
