| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pchan(at)contigo(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 |
| Date: | 2013-01-22 01:53:05 |
| Message-ID: | 4542.1358819585@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pius Chan | 2013-01-22 04:44:40 | Re: BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 |
| Previous Message | pchan | 2013-01-22 00:31:21 | BUG #7819: missing chunk number 0 for toast value 1235919 in pg_toast_35328 |