From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | josh(at)agliodbs(dot)com |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [pgsql-advocacy] Avoiding upgrade backlash |
Date: | 2007-11-17 05:47:27 |
Message-ID: | 10223.1195278447@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-docs |
Josh Berkus <josh(at)agliodbs(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paesold | 2007-11-17 08:25:13 | Re: [pgsql-advocacy] Redirects for gborg are in place |
Previous Message | Josh Berkus | 2007-11-17 05:07:17 | Re: [pgsql-advocacy] Avoiding upgrade backlash |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-11-17 11:34:49 | Re: [pgsql-advocacy] Avoiding upgrade backlash |
Previous Message | Josh Berkus | 2007-11-17 05:07:17 | Re: [pgsql-advocacy] Avoiding upgrade backlash |