Re: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

Hi Tom,

Yes, we start seeing this ERROR after upgrade to 9.1.7. The ERROR is from the "cluster jms_messages" command. Last night, the ERROR happened three times:

(1) at 00:20:01
ERROR: missing chunk number 0 for toast value 1239124 in pg_toast_35328

(2) at 00:25:01
ERROR: missing chunk number 0 for toast value 1239124 in pg_toast_35328

(3) at 00:35:01
ERROR: missing chunk number 0 for toast value 1241022 in pg_toast_35328

The "cluster jms_messages" runs every 5 minutes. However, so far, it seems that the ERROR happens at about mid-night and 35328 is the toast area of the "jms_message" table:

-[ RECORD 1 ]-+-------------
oid | 35328
relname | jms_messages
reltoastrelid | 35331
reltoastidxid | 0

Thanks a lot,

Pius
________________________________________
From: Tom Lane [tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, January 21, 2013 5:53 PM
To: Pius Chan
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328

pchan(at)contigo(dot)com writes:
> We just upgraded from PostgreSQL 9.1.3 to 9.1.7 last week.

Are you saying this error started to appear just after the upgrade? Or
was it there before?

> In our database
> cluster, one database is used by the Java Message Service (JMS) system. One
> table in the database "jms_messages", is inserted, updated and then deleted
> frequently. For every five minutes, we have a cron job to "cluster
> jms_messages; analyze jms_messages". About once per day, we go the above
> ERROR and I check that pg_toast_35328 is the toast area of the jms_messages
> table.

Is that error coming from the CLUSTER operations, or other commands? Is
it persisting across (successful) CLUSTERs? Is it always the same toast
value OID that's being complained of?

regards, tom lane