From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Andres Freund <andres@2ndquadrant.com>
Cc: Bernhard Schrader <bernhard.schrader@innogames.de>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [ADMIN] Problems with enums after pg_upgrade
Date: Tue, 18 Dec 2012 15:38:13 -0500
Message-ID: <9230.1355863093@sss.pgh.pa.us> (raw)
In-Reply-To: <50D0CFF7.5030606@dunslane.net>
References: <50CEFE95.9040301@innogames.de>
<20121218014137.GB29143@momjian.us>
<50D02D13.3010004@innogames.de>
<50D0914E.3040508@dunslane.net>
<20121218162256.GA24700@momjian.us>
<50D0B0AD.9010905@innogames.de>
<11487.1355855052@sss.pgh.pa.us>
<20121218183916.GA7666@awork2.anarazel.de>
<12773.1355859273@sss.pgh.pa.us>
<50D0C80D.90806@dunslane.net>
<13661.1355860724@sss.pgh.pa.us>
<50D0CFF7.5030606@dunslane.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Andrew Dunstan <andrew@dunslane.net> writes:
> People have been known to hack pg_enum on their own, especially before
> we added enum extension.
> Of course, if they do that they get to keep both pieces.
Yeah ... this would be very readily explainable if there had been a
manual deletion from pg_enum somewhere along the line. Even if there
were at that time no instances of the OID left in tables, there could
be some in upper btree pages. They'd have caused no trouble in 9.0
but would (if odd) cause trouble in 9.2.
Of course, this theory doesn't explain why the problem was seen on some
copies and not others cloned from the same database --- unless maybe
there had been an index page split on the master in between the
clonings, and that moved the troublesome OID into a position where it
was more likely to get compared-to. That's not a hugely convincing
explanation though.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: tgl@sss.pgh.pa.us, andrew@dunslane.net, andres@2ndquadrant.com, bernhard.schrader@innogames.de, bruce@momjian.us, pgsql-hackers@postgresql.org
Subject: Re: [ADMIN] Problems with enums after pg_upgrade
In-Reply-To: <9230.1355863093@sss.pgh.pa.us>
* 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