Re: [ADMIN] Problems with enums after pg_upgrade - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [ADMIN] Problems with enums after pg_upgrade
Date
Msg-id 20121219155646.GA5910@awork2.anarazel.de
Whole thread Raw
In response to Re: [ADMIN] Problems with enums after pg_upgrade  (Bernhard Schrader <bernhard.schrader@innogames.de>)
Responses Re: [ADMIN] Problems with enums after pg_upgrade  (Andrew Dunstan <andrew@dunslane.net>)
Re: [ADMIN] Problems with enums after pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2012-12-19 16:51:32 +0100, Bernhard Schrader wrote:
> Hello again,
>
> well, still everything is working.
>
> What information do you need to get into this issue?
>
> Well, so far i can say, we dont use ALTER TYPE ADD VALUE. We use some more
> or less changed enum_add and enum_del (Which are appended at the end) to be
> able to change enums within transactions.

That explains everything. You *CANNOT* do that. There are some pretty
fundamental reasons why you are not allowed to add enums in a
transaction. And even more reasons why deleting from enums isn't allowed
at all.

Greetings,

Andres Freund

--Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Bernhard Schrader
Date:
Subject: Re: [ADMIN] Problems with enums after pg_upgrade
Next
From: Pavan Deolasee
Date:
Subject: Re: Set visibility map bit after HOT prune