Skip site navigation (1) Skip section navigation (2)

Re: pg_upgrade issues

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: depstein(at)alliedtesting(dot)com, pgsql-bugs(at)postgresql(dot)org, pgagarinov(at)alliedtesting(dot)com
Subject: Re: pg_upgrade issues
Date: 2010-07-26 13:44:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Robert Haas wrote:
> On Sat, Jul 24, 2010 at 11:37 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> I am inclined to prevent pg_upgrade from migrating any database that
> >> uses any of these reg* data types, and document this restriction. ?I
> >> probably could allow regtype because that pg_type is preserved.
> >
> > I have applied the attached patch to CVS HEAD and 9.0 that prevent
> > migration when any reg* data type is used in a user table (except
> > regtype because pg_type.oid is preserved).
> This is a good change; however, there is still some potential for
> lossage here.  What if the column were declared as type OID?  Then it
> would be hard to tell whether migration was safe or not.  Perhaps the
> right long-term solution is to try harder to preserve OIDs in more
> cases.

You are right that an oid column cannot be tracked easily.  It could
refer to a user table with oids, or it might be a system row reference.

I have considered preserving more oids, but that is going to increase
the backend changes for pg_upgrade, and I am hesistant to do that until
there is a claarer demand.

  Bruce Momjian  <bruce(at)momjian(dot)us>

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

In response to

pgsql-bugs by date

Next:From: Tizziano PereaDate: 2010-07-26 14:25:49
Subject: BUG #5572: Error Trying to connec from Crystal Reports to Sever PostgreSQL
Previous:From: Robert HaasDate: 2010-07-26 12:56:16
Subject: Re: pg_upgrade issues

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group