From: | Lou Picciano <loupicciano(at)comcast(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | toast error after pg_upgrade 9.0.4 -> 9.1rc1 |
Date: | 2011-08-31 20:11:15 |
Message-ID: | 239726088.702769.1314821475533.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
After running an essentially uneventful* pg_upgrade from 9.0.4 -> 9.1rc1, we are seeing some toast errors logged on the new cluster:
All are of this pattern: ERROR: missing chunk number 0 for toast value 130087 in pg_toast_34735
Have seen the same pattern for a few of the databases in the 9.1rc1 cluster, and all as a result of a select on a usr table (the offending SELECT happens to be the first one any of these DBs sees, as it's the first step in a user authentication process). SELECT count(*) does not produce an error.
*almost uneventful: We also saw messages that the destination cluster did not have one of our schema - (of course it didn't!) - I didn't realize pg_upgrade doesn't 'do' schema?
Lou Picciano
From | Date | Subject | |
---|---|---|---|
Next Message | Marcos Hercules Santos | 2011-08-31 22:39:36 | function on trigger |
Previous Message | Ben Chobot | 2011-08-31 18:53:39 | Re: regression between 8.4.8 and 8.4.2? |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-08-31 20:24:33 | Re: [COMMITTERS] pgsql: Ensure that contrib/pgstattuple functions respond to cancel |
Previous Message | Alvaro Herrera | 2011-08-31 20:03:25 | Re: pg_restore --no-post-data and --post-data-only |