Re: pg_upgrade

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hp(dot)com>
Cc: Tory M Blue <tmblue(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: pg_upgrade
Date: 2011-12-05 15:34:54
Message-ID: 201112051534.pB5FYsm28466@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Nicholson, Brad (Toronto, ON, CA) wrote:
> > -----Original Message-----
> > From: Bruce Momjian [mailto:bruce(at)momjian(dot)us]
> > Sent: Monday, December 05, 2011 10:24 AM
> > To: Nicholson, Brad (Toronto, ON, CA)
> > Cc: Tory M Blue; pgsql-performance(at)postgresql(dot)org; Magnus Hagander
> > Subject: Re: [PERFORM] pg_upgrade
> >
> > Nicholson, Brad (Toronto, ON, CA) wrote:
> > > > 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.
> >
> > Checking for all such cases would make pg_upgrade huge and unusable.
> > If
> > you messed up your configuration, pg_upgrade can't check for every such
> > case. There are thosands of ways people can mess up their
> > configuration.
>
> Based on the OP this does not seem like a messed up configuration. It
> sounds like the OP used a fully supported core feature of Postgres
> (tablespaces) and pg_upgrade failed as a result. I think having our
> upgrade utility fail under such circumstances is a bad thing.

The OP has not indicated exactly what he did to move the tablespaces, so
I have to assume he changed the SQL location but not the symbolic link
location, or some other misconfiguration. Can someone provide the steps
that caused the failure?

pg_upgrade works fine for tablespaces so there must be something
different about his configuration. Unless I hear details, I have to
assume the tablespace move was done incorrectly. This is the first
tablespace failure like this I have ever gotten, and I do test
tablespaces. Perhaps something is wrong, but I can't guess what it is.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

  • Re: pg_upgrade at 2011-12-05 15:29:00 from Nicholson, Brad (Toronto, ON, CA)

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Ernesto Quiñones 2011-12-05 17:19:42 Re: Question about VACUUM
Previous Message Nicholson, Brad (Toronto, ON, CA) 2011-12-05 15:29:00 Re: pg_upgrade