BUG #19608: Error while Reindexing Main Table
The following bug has been logged on the website:
Bug reference: 19608
Logged by: Kirti Kumar
Email address: kirtikumarkk21@gmail.com
PostgreSQL version: 17.9
Operating system: Linux
Description:
REINDEX TABLE CONCURRENTLY leaves corrupted TOAST index unresolved; explicit
REINDEX INDEX on TOAST index fixes "missing chunk number" errorr
ERROR processing traceable: missing chunk number 0 for toast value
1040152679 in pg_toast_16499
On Mon, Aug 03, 2026 at 09:54:17AM +0000, PG Bug reporting form wrote:
REINDEX TABLE CONCURRENTLY leaves corrupted TOAST index unresolved; explicit
REINDEX INDEX on TOAST index fixes "missing chunk number" errorr
ERROR processing traceable: missing chunk number 0 for toast value
1040152679 in pg_toast_16499
This may point to a bug, however you are giving no information except
the error, meaning that one has no pointers. One thing that could
count here is what kind of workload is running in parallel of the
failing REINDEX CONCURRENTLY, for example. Having a reproducible test
case would be of course nicer.
--
Michael