From: Andres Freund <andres@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bernhard Schrader <bernhard.schrader@innogames.de>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [ADMIN] Problems with enums after pg_upgrade
Date: Tue, 18 Dec 2012 19:39:16 +0100
Message-ID: <20121218183916.GA7666@awork2.anarazel.de> (raw)
In-Reply-To: <11487.1355855052@sss.pgh.pa.us>
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 2012-12-18 13:24:12 -0500, Tom Lane wrote:
> Bernhard Schrader <bernhard.schrader@innogames.de> writes:
> > Beside of that, we tested a little bit more with the failing query:
> > The statement which is causing the error is a big UPDATE-statement with
> > FROM. After some testing we figured out that the subselect in the
> > FROM-clause is working fine. And if we simplify the UPDATE-statement
> > it's also working. We're able to show the data and we're able to do
> > simple updates on the table. But the two things combined are not
> > working.
>
> Does the table being updated have any indexes on enum columns? I'm
> suspicious that the bogus OID is in an index page somewhere, and not
> in the table at all.
I already wondered whether it could be a problem caused by pg_upgrade
not ignoring invalid indexes until recently, but I don't really see how
it could cause an invalid oid to end up in the index.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
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: andres@2ndquadrant.com, tgl@sss.pgh.pa.us, bernhard.schrader@innogames.de, bruce@momjian.us, andrew@dunslane.net, pgsql-hackers@postgresql.org
Subject: Re: [ADMIN] Problems with enums after pg_upgrade
In-Reply-To: <20121218183916.GA7666@awork2.anarazel.de>
* 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