Re: pg_upgrade

From: "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hp(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>, Tory M Blue <tmblue(at)gmail(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: pg_upgrade
Date: 2011-12-05 13:36:36
Message-ID: EC55DC235432104F8255702A8D7344D925700286@G9W0741.americas.hpqcorp.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> -----Original Message-----
> From: pgsql-performance-owner(at)postgresql(dot)org [mailto:pgsql-performance-
> owner(at)postgresql(dot)org] On Behalf Of Bruce Momjian
> Sent: Saturday, December 03, 2011 6:42 PM
> To: Tory M Blue
> Cc: pgsql-performance(at)postgresql(dot)org
> Subject: Re: [PERFORM] pg_upgrade
>
> Tory M Blue wrote:
> > On Sat, Dec 3, 2011 at 6:04 AM, Bruce Momjian <bruce(at)momjian(dot)us>
> wrote:
> >
> > > Well, I am not totally clear how you are moving things around, but
> I do
> > > know pg_upgrade isn't happy to have the old and new cluster be very
> > > different.
> > >
> > > What I think is happening is that you didn't properly move the
> > > tablespace in the old cluster. ?We don't give you a very easy way
> to do
> > > that. ?You need to not only move the directory, but you need to
> update
> > > the symlinks in data/pg_tblspc/, and update the pg_tablespace
> system
> > > table. ?Did you do all of that? ?Does the 8.4 server see the
> tablespace
> > > properly after the move, but before pg_upgrade?
> >
> >
> > Simple answer is umm no..
>
> The "no" is an answer to which question?
>
> > "http://www.postgresql.org/docs/current/static/pgupgrade.html" is
> > obviously lacking than :)
> >
> > Soooo I can take what you have told me and see if I can't attempt to
> > make those things happen and try again. Makes sense, but boy that's a
> > large piece of info missing in the document!
>
> You mean moving tablespaces? That isn't something pg_upgrade deals
> with. If we need docs to move tablespaces, it is a missing piece of
> our
> main docs, not something pg_upgrade would ever mention.

If I'm reading the issue correctly, and pg_upgrade gets part way through an upgrade then fails if it hits a tablespace - it seems to me like the pg_upgrade should check for such a condition at the initial validation stage not proceed if found.

Brad.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2011-12-05 15:19:15 Re: Intersect/Union X AND/OR
Previous Message Thiago Godoi 2011-12-05 12:14:04 Re: Intersect/Union X AND/OR