From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-advocacy@postgresql.org
Cc: josh@agliodbs.com
Cc: pgsql-docs@postgresql.org
Subject: Re: Avoiding upgrade backlash
Date: Tue, 13 Nov 2007 11:05:18 +0100
Message-ID: <473976DE.4040404@kaltenbrunner.cc> (raw)
In-Reply-To: <200711131045.04878.peter_e@gmx.net>
References: <200711121442.31233.josh@agliodbs.com>
<200711131045.04878.peter_e@gmx.net>
Peter Eisentraut wrote:
> Am Montag, 12. November 2007 schrieb Josh Berkus:
>> I'm thinking that we need to warn everyone about:
>> 1) They need to use 8.3's pg_dump, not the old version, to upgrade (this is
>> always true but now doing it wrong will break a lot more users).
>
> What difference would pg_dump make?
well the current problem is that either way pg_dump can generate dumps
that are not restorable without modification on 8.3 (like say one that
contains a VIEW that does a INTEGER = TEXT comparision which 8.3 will
refuse to create) even if dumped with 8.3.
>
>> 2) They need to check for bugs
>
> What bugs?
queries that depend on implict casts "just working" - most of those are
actually bug or maybe sloppy coding on the application side but it is
imho by FAR the most incompatible behaviour change we have done in the
last few releases.
I guess that the largest amount of these are TEXT/INTEGER casts and the
kind of app that will probably hit most are the ones that are
misbehaving anyway (think EAV style stuff) - but it is a incompatible
change nevertheless.
>
>> 3) If Robert gets his type-cast backport package together, the location of
>> that.
>
> Well, if you want to undo the changes, you don't need a backport package; you
> can just change the cast's definition.
well the point here is that we ought to be more open about the impact of
the change and i think that the release notes need to mention that (and
maybe also an example on how to change/re-add the casts)
Stefan
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: stefan@kaltenbrunner.cc, peter_e@gmx.net, pgsql-advocacy@postgresql.org, josh@agliodbs.com
Subject: Re: Avoiding upgrade backlash
In-Reply-To: <473976DE.4040404@kaltenbrunner.cc>
* 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