| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bernhard Schrader <bernhard(dot)schrader(at)innogames(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [ADMIN] Problems with enums after pg_upgrade |
| Date: | 2012-12-19 15:56:46 |
| Message-ID: | 20121219155646.GA5910@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2012-12-19 15:56:57 | Re: Set visibility map bit after HOT prune |
| Previous Message | Bernhard Schrader | 2012-12-19 15:51:32 | Re: [ADMIN] Problems with enums after pg_upgrade |