Re: [ADMIN] Problems with enums after pg_upgrade

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Bernhard Schrader <bernhard(dot)schrader(at)innogames(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [ADMIN] Problems with enums after pg_upgrade
Date: 2012-12-19 17:13:03
Message-ID: 18042.1355937183@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> what is even worse is that this procedure doesn't take any care at all
> of the ordering rule for even numbered enum oids.

Good point. You really should use ALTER TYPE ADD VALUE, on versions
where that's available.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-12-19 17:25:45 Re: Review of Row Level Security
Previous Message Robert Haas 2012-12-19 17:10:04 Re: Set visibility map bit after HOT prune