From: Josh Berkus <josh@agliodbs.com>
To: pgsql-advocacy@postgresql.org
Cc: pgsql-docs@postgresql.org
Subject: Avoiding upgrade backlash
Date: Mon, 12 Nov 2007 14:42:30 -0800
Message-ID: <200711121442.31233.josh@agliodbs.com> (raw)
Hackers,
I'm seeing from reports on IRC that 8.3 may cause an unprecedented number
of upgrade issues for users who have old, badly-written applications.
Stefan K, for example, was reporting the necessity of re-writing 3000
lines of his PL/pgSQL code on an older app (about 10%).
While we are right to choke down abuse of implicit casting, it might be a
good idea to give users stronger warnings and instructions.
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).
2) They need to check for bugs
3) If Robert gets his type-cast backport package together, the location of
that.
I'm thinking this warning should go (prominently) into the release notes,
the community notice, and the extended web release.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
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: josh@agliodbs.com, pgsql-advocacy@postgresql.org
Subject: Re: Avoiding upgrade backlash
In-Reply-To: <200711121442.31233.josh@agliodbs.com>
* 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