From: Peter Koczan <pjkoczan@gmail.com>
To: Peter Koczan <pjkoczan@gmail.com>
Cc: Steve Holdoway <steve.holdoway@firetrust.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: upgrade 8.0.3 -> 8.2.4
Date: Thu, 10 May 2007 18:45:38 -0500
Message-ID: <4643AEA2.4050404@gmail.com> (raw)
In-Reply-To: <4544e0330705100826v1159a7aewedab249e9c77fdbb@mail.gmail.com>
References: <20070510170751.348e09a6.steve.holdoway@firetrust.com>
<4544e0330705100826v1159a7aewedab249e9c77fdbb@mail.gmail.com>
I almost forgot one of the biggest gotchas. Remember that users and
groups were conflated into "roles" in postgres 8.1. In addition to being
a change, there were some other issues, namely that you couldn't
manually specify user and group sysids. I had to change our user and
group management scripts to properly reflect this.
Peter
Peter Koczan wrote:
> A few months ago, I upgraded postgres from 7.4 to 8.2. There were a
> few gotchas, but we don't keep a whole lot of data so even the biggest
> problems were, on the whole, minor.
>
> - The cidr data type became more strict, and a few tables in our
> network database would not restore until this was fixed.
> - One of the primary keys broke and couldn't get created. This was
> more the fault of poor admins (before my time) and internal
> fragmentation than postgres 7.4. I had to fix the underlying table
> before it would restore.
> - There were a few permissions issues (new acls + an inconsistent
> previous policy = fun).
> - The system databases went from SQL_ASCII encoding to UTF8 encoding.
> I had to explicitly create the database during the restore, or else
> the database would have the wrong encoding.
>
> I doubt that you will run into these exact problems, but my point is
> that there are inevitably some gotchas. If it's not prohibitively
> time-consuming, I'd recommend a full dump/restore of your database(s)
> from 8.0 to 8.2 so you can catch many of these gotchas before going
> live. Also, you might want to create test versions of your apps and
> try them against the 8.2 server.
>
> On the whole, I've found postgres to be very good at maintaining
> backwards compatibility of interfaces and sql, so I estimate that most
> queries and db apps should "just work" with 8.2.
>
> Peter
>
> On 5/10/07, *Steve Holdoway* <steve.holdoway@firetrust.com
> <mailto:steve.holdoway@firetrust.com>> wrote:
>
> Are there any gotchas? I've got the opportunity to move to another
> database server for this application and yould like to take the
> opportunity to upgrade at the same time.
>
> tia,
>
> Steve
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>
>
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-admin@postgresql.org
Cc: pjkoczan@gmail.com, steve.holdoway@firetrust.com
Subject: Re: upgrade 8.0.3 -> 8.2.4
In-Reply-To: <4643AEA2.4050404@gmail.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