Re: unexpected chunk number 2 (expected 0) for toast value ... in pg_toast_18536

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: Jan Wieck <jan(at)wi3ck(dot)info>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: unexpected chunk number 2 (expected 0) for toast value ... in pg_toast_18536
Date: 2020-03-15 21:18:28
Message-ID: 20200315211828.GP467@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Mar 15, 2020 at 05:04:06PM -0400, Jan Wieck wrote:

> Have you tried to reindex the table? Toast internally forces an index scan,
> so missing index tuples or an otherwise corrupted toast index would have
> the same symptoms as toast chunks actually missing.

We sure did, but thanks for reminding.

Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Björn Lundin 2020-03-15 21:33:35 Order by and timestamp
Previous Message Jan Wieck 2020-03-15 21:04:06 Re: unexpected chunk number 2 (expected 0) for toast value ... in pg_toast_18536