pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: pgsql-docs@postgresql.org
Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash
Date: Sat, 17 Nov 2007 00:47:27 -0500
Message-ID: <10223.1195278447@sss.pgh.pa.us> (raw)
In-Reply-To: <200711162107.17437.josh@agliodbs.com>
References: <200711152000.lAFK08911889@momjian.us>
	<200711162107.17437.josh@agliodbs.com>

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



view thread (37+ messages)  latest in thread

Message-ID: <10223.1195278447@sss.pgh.pa.us>
Permalink:  ../10223.1195278447@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10223.1195278447@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
  Subject: Re: [pgsql-advocacy] Avoiding upgrade backlash
  In-Reply-To: <10223.1195278447@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox