Re: pg_upgrade docs - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade docs
Date
Msg-id 201005241743.o4OHh2p28204@momjian.us
Whole thread Raw
In response to Re: pg_upgrade docs  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: pg_upgrade docs
List pgsql-hackers
Stefan Kaltenbrunner wrote:
> On 05/19/2010 05:16 PM, Bruce Momjian wrote:
> > Andres Freund wrote:
> >> On Wednesday 19 May 2010 22:39:32 Bruce Momjian wrote:
> >>> There are some limitations when migrating from 8.3 to 8.4, but not when
> >>> migrating from 8.3 to 9.0, because we added a feature to 9.0.  Can you
> >>> give a specific example?
> >> Didnt the 'name' alignment change?
> > 
> > Uh, the heading above that item is:
> > 
> >   <title>Limitations in migrating <emphasis>from</> PostgreSQL
> >   8.3</title>
> > 
> > What is unclear there?  It covers going to 8.4 and 9.0.
> 
> well the wording makes it kinda unclear on what happens if you go FROM
> 8.4 to 9.0. If there are no known limits we might want to add a small
> note saying so. If there are some we might want to restructure the
> paragraph a bit...

Sorry for the delay in replying.  The section you list is titled:
F.31.4. Limitations in migrating from PostgreSQL 8.3
http://developer.postgresql.org/pgdocs/postgres/pgupgrade.html

and the first sentence is:
  pg_upgrade will not work for a migration from 8.3 if a user column

I have updated the paragraph to be:
  Upgrading from PostgreSQL 8.3 has additional restrictions not present  when upgrading from later PostgreSQL releases.
For example,  pg_upgrade will not work for a migration from 8.3 if a user column  is defined as:
 

Can you suggest other wording?

FYI, the items that affect only 8.3 to 8.4 migrations are no longer in
the 9.0 pg_upgrade docs because we don't support 8.4 as a target
anymore;  specifically:
Limitations In Migrating _to_ PostgreSQL 8.4----------------------------------------------------------pg_migrator will
notwork if a user column is defined as:    o  a user-defined composite data type    o  a user-defined array data type
o  a user-defined enum data typeYou must drop any such columns and migrate them manually.
 

You can see the full documentation here:
http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-migrator/pg_migrator/README?rev=1.78&content-type=text/x-cvsweb-markup

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Move 'long long' check to c.h
Next
From: Bruce Momjian
Date:
Subject: Re: beta testing - pg_upgrade bug fix - double free