Re: missing chunk number 0 for toast value - Mailing list pgsql-general

From Ed L.
Subject Re: missing chunk number 0 for toast value
Date
Msg-id 200504271716.38630.pgsql@bluepolka.net
Whole thread Raw
In response to Re: missing chunk number 0 for toast value  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: missing chunk number 0 for toast value  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Wednesday April 27 2005 4:40 pm, Tom Lane wrote:
> "Ed L." <pgsql@bluepolka.net> writes:
> > On Wednesday April 27 2005 3:55 pm, Tom Lane wrote:
> >> Have you tried REINDEXing the toast table in question?
> >
> > Not yet.  Any way to repair it without blocking concurrent
> > access?
>
> Unlikely.  But the lock will only affect operations that need
> to touch toasted field values.

Does this shed any light?  pg_toast_6221538 is the relevant toast
table...

$ psql -c "set enable_indexscan=off; select chunk_seq,
length(chunk_data) from pg_toast.pg_toast_6221538 where chunk_id
= 19319495 order by chunk_seq;"
 chunk_seq | length
-----------+--------
(0 rows)

$ psql -c "select chunk_seq, length(chunk_data) from
pg_toast.pg_toast_6221538 where chunk_id = 19319495 order by
chunk_seq;"
 chunk_seq | length
-----------+--------
(0 rows)

Ed

pgsql-general by date:

Previous
From: "Uwe C. Schroeder"
Date:
Subject: Re: restarting after power outage
Next
From: Tzahi Fadida
Date:
Subject: SPI cursors pinned buffer and moving to the first tuple.