Re: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328
Date
Msg-id 4542.1358819585@sss.pgh.pa.us
Whole thread Raw
In response to BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328  (pchan@contigo.com)
Responses Re: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328
Re: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328
List pgsql-bugs
pchan@contigo.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

pgsql-bugs by date:

Previous
From: pchan@contigo.com
Date:
Subject: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328
Next
From: Pius Chan
Date:
Subject: Re: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328