Re: [pgsql-advocacy] Avoiding upgrade backlash - Mailing list pgsql-docs

From Tom Lane
Subject Re: [pgsql-advocacy] Avoiding upgrade backlash
Date
Msg-id 10223.1195278447@sss.pgh.pa.us
Whole thread Raw
In response to Re: [pgsql-advocacy] Avoiding upgrade backlash  (Josh Berkus <josh@agliodbs.com>)
Responses Re: [pgsql-advocacy] Avoiding upgrade backlash  (Bruce Momjian <bruce@momjian.us>)
List pgsql-docs
Josh Berkus <josh@agliodbs.com> writes:
> Hmmm.  I don't feel like it contains a clear warning, though.  We need a
> statement like:

> Some users may encounter issues upgrading due to the changes in handling
> data type casts.  If you suspect that your schema or application may not
> be handling data type comparisons cleanly, you are strongly urged to test
> for casting error messages before upgrading your production server.

When have we ever suggested that people *shouldn't* test their apps
before committing to a major version update?

I think the whole thing has been significantly overblown.  We have made
incompatible changes bigger than this one --- and, often, harder to find
let alone fix --- in almost every major release.  This one you can at
least be pretty sure that you will get an error, and not a silent change
in behavior, if you fall foul of it.

            regards, tom lane

pgsql-docs by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash
Next
From: Bruce Momjian
Date:
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash