| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| 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-18 02:10:23 |
| Message-ID: | 20121218021023.GC29143@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On Mon, Dec 17, 2012 at 12:14:29PM +0100, Bernhard Schrader wrote:
> Hello together,
>
> last thursday I upgraded one of our 9.0.6 postgresql servers to
> 9.2.2 with pg_upgrade. So far everything seemed to work but we now
> discover problems with the enum types. If we run one specific query
> it breaks all time with such an error message:
>
> ERROR: invalid internal value for enum: 520251
>
> if this number should represent the enumtypid it is not existing
> anymore in pg_enum.
>
> How could i solve this problem? should we regenerate all enums? or
> what could we do?
> Hopefully anyone has a clue, google doesn't seem to be the ressource
> for this problem.
Can anyone suggest why enum upgrade is failing for this user? What
should he be checking for?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jay Newman | 2012-12-18 04:01:24 | pg_basebackup over slowed connection , slowed out of proportion |
| Previous Message | Bruce Momjian | 2012-12-18 01:41:37 | Re: [ADMIN] Problems with enums after pg_upgrade |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2012-12-18 02:21:12 | Re: Enabling Checksums |
| Previous Message | Robert Haas | 2012-12-18 02:00:37 | Re: Parser Cruft in gram.y |