| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | loganathan P <plogandba(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Application Error When Accessing the Table – PostgreSQL 15.18 |
| Date: | 2026-11-04 15:03:54 |
| Message-ID: | 1589010.1793804634@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Wed, 2026-11-04 at 11:52 +0530, loganathan P wrote:
>> While accessing the table through the application, I encountered the following error.
>> ERROR - missing chunk number 0 for toast value 55195659 in pg_toast_171559.
> This is data corruption.
Indeed, but you might be able to get out of it by REINDEX'ing that
toast table, especially if you recently used REINDEX CONCURRENTLY
on it. There's a recently-fixed bug that could lead to damaged
toast indexes, though fortunately not to corruption of the tables
themselves.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | loganathan P | 2026-11-05 02:53:05 | Re: Application Error When Accessing the Table – PostgreSQL 15.18 |
| Previous Message | loganathan P | 2026-11-04 14:04:45 | Re: Application Error When Accessing the Table– PostgreSQL 15.18 |