Application Error When Accessing the Table – PostgreSQL 15.18

Поиск
Список
Период
Сортировка
Искать

Application Error When Accessing the Table – PostgreSQL 15.18

От:
loganathan P <plogandba@gmail.com>
Дата:
Dear All,


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.


Thanks,


Regards,

Loganathan P

Re: Application Error When Accessing the Table – PostgreSQL 15.18

От:
rob stone <floriparob@tpg.com.au>
Дата:
Hello,

On Wed, 2026-11-04 at 11:52 +0530, loganathan P wrote:
> Dear All,
> 
> 
> 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.
> 
> 
> Thanks,
> 
> 
> Regards,
> 
> Loganathan P


That error is usually caused by corruption.

Postgres V15. Did you create the database with checksums enabled?
It is enabled by default from V18 -- current production version.

This post might be helpful.

https://gist.github.com/supix/80f9a6111dc954cf38ee99b9dedf187a

HTH,
Robert




Re: Application Error When Accessing the Table – PostgreSQL 15.18

От:
Laurenz Albe <laurenz.albe@cybertec.at>
Дата:
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.

If you have a good backup, that's the easiest solution.

Other than that, identify the row that causes the error and delete it.

After you got rid of all the visible symptoms of corruption, dump
and restore the database to a newly created cluster - that will get
rid of any lurking corruption.

Yours,
Laurenz Albe


Re: Application Error When Accessing the Table– PostgreSQL 15.18

От:
loganathan P <plogandba@gmail.com>
Дата:



Dear All,

Postgres V15. Did you create the database with checksums enabled?

Answer :- No, the database was not created with data checksums enabled. Please let me know what the next steps are for recovering the corrupted table without backup.


Thanks.


Regards,
Loganathan P





On Wed, Nov 4, 2026 at 12:59 PM rob stone <floriparob@tpg.com.au> wrote:
Hello,

On Wed, 2026-11-04 at 11:52 +0530, loganathan P wrote:
> Dear All,
>
>
> 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.
>
>
> Thanks,
>
>
> Regards,
>
> Loganathan P


That error is usually caused by corruption.

Postgres V15. Did you create the database with checksums enabled?
It is enabled by default from V18 -- current production version.

This post might be helpful.

https://gist.github.com/supix/80f9a6111dc954cf38ee99b9dedf187a

HTH,
Robert


Re: Application Error When Accessing the Table – PostgreSQL 15.18

От:
Tom Lane <tgl@sss.pgh.pa.us>
Дата:
Laurenz Albe  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


Re: Application Error When Accessing the Table – PostgreSQL 15.18

От:
loganathan P <plogandba@gmail.com>
Дата:
Dear All,

While attempting to delete the corrupted rows, I am encountering the following error.


ERROR: tuple already updated by self.


Thanks.


Regards,

Loganathan P



On Wed, 4 Nov, 2026, 8:37 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:
Laurenz Albe <laurenz.albe@cybertec.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

Re: Application Error When Accessing the Table – PostgreSQL 15.18

От:
Ron Johnson <ronljohnsonjr@gmail.com>
Дата:
Try deleting that one row.  Or exporting every row of the table except that one row.  (Then recreate the table and import.)

On Wed, Nov 4, 2026 at 9:53 PM loganathan P <plogandba@gmail.com> wrote:
Dear All,

While attempting to delete the corrupted rows, I am encountering the following error.


ERROR: tuple already updated by self.


Thanks.


Regards,

Loganathan P



On Wed, 4 Nov, 2026, 8:37 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:
Laurenz Albe <laurenz.albe@cybertec.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


--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
FAQ