Application Error When Accessing the Table – PostgreSQL 15.18

Started by loganathan P18 days ago7 messagesgeneral
Jump to latest
#1loganathan 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

#2rob stone
floriparob@tpg.com.au
In reply to: loganathan P (#1)
Re: Application Error When Accessing the Table – PostgreSQL 15.18

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

#3Laurenz Albe
laurenz.albe@cybertec.at
In reply to: loganathan P (#1)
Re: Application Error When Accessing the Table – PostgreSQL 15.18

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

#4loganathan P
plogandba@gmail.com
In reply to: loganathan P (#1)
Re: Application Error When Accessing the Table– PostgreSQL 15.18

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:

Show quoted text

[image: Boxbe] <https://www.boxbe.com/overview> rob stone (
floriparob@tpg.com.au) is not on your Guest List
<https://www.boxbe.com/approved-list?tc_serial=61984369953&tc_rand=852181494&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&key=sQvI%2FZ0g%2BfQDUqUdXrphBAMhiFC0NvzsaAmfe5y32Pk%3D&token=wOVr7Lg3HI0sNnLdMqI3qOb0UVkab%2B9WCN2pond7s3h1dwHEtnlZlufsRDSh7ahd>
| Approve sender
<https://www.boxbe.com/anno?tc_serial=61984369953&tc_rand=852181494&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&key=sQvI%2FZ0g%2BfQDUqUdXrphBAMhiFC0NvzsaAmfe5y32Pk%3D&token=wOVr7Lg3HI0sNnLdMqI3qOb0UVkab%2B9WCN2pond7s3h1dwHEtnlZlufsRDSh7ahd>
| Approve domain
<https://www.boxbe.com/anno?tc_serial=61984369953&tc_rand=852181494&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&dom&key=sQvI%2FZ0g%2BfQDUqUdXrphBAMhiFC0NvzsaAmfe5y32Pk%3D&token=wOVr7Lg3HI0sNnLdMqI3qOb0UVkab%2B9WCN2pond7s3h1dwHEtnlZlufsRDSh7ahd>
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

#5Tom Lane
tgl@sss.pgh.pa.us
In reply to: Laurenz Albe (#3)
Re: Application Error When Accessing the Table – PostgreSQL 15.18

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

#6loganathan P
plogandba@gmail.com
In reply to: Laurenz Albe (#3)
Re: Application Error When Accessing the Table – PostgreSQL 15.18

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:

Show quoted text

[image: Boxbe] <https://www.boxbe.com/overview> Tom Lane (
tgl@sss.pgh.pa.us) is not on your Guest List
<https://www.boxbe.com/approved-list?tc_serial=61984809141&tc_rand=2014793862&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&key=JQ3tI3eduxxJHzt5mWVx32Pxo0jpUjHoGr0HJMHGZ8M%3D&token=%2Fs%2FcOiPbIzNdXQbLqZPDKmB02RANtTOkdwAPYI6vKjfUfuEQcHyroNRtyvL5lr5W>
| Approve sender
<https://www.boxbe.com/anno?tc_serial=61984809141&tc_rand=2014793862&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&key=JQ3tI3eduxxJHzt5mWVx32Pxo0jpUjHoGr0HJMHGZ8M%3D&token=%2Fs%2FcOiPbIzNdXQbLqZPDKmB02RANtTOkdwAPYI6vKjfUfuEQcHyroNRtyvL5lr5W>
| Approve domain
<https://www.boxbe.com/anno?tc_serial=61984809141&tc_rand=2014793862&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&dom&key=JQ3tI3eduxxJHzt5mWVx32Pxo0jpUjHoGr0HJMHGZ8M%3D&token=%2Fs%2FcOiPbIzNdXQbLqZPDKmB02RANtTOkdwAPYI6vKjfUfuEQcHyroNRtyvL5lr5W>
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

#7Ron
ronljohnsonjr@gmail.com
In reply to: loganathan P (#6)
Re: Application Error When Accessing the Table – PostgreSQL 15.18

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:

[image: Boxbe] <https://www.boxbe.com/overview> Tom Lane (
tgl@sss.pgh.pa.us) is not on your Guest List
<https://www.boxbe.com/approved-list?tc_serial=61984809141&tc_rand=2014793862&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&key=JQ3tI3eduxxJHzt5mWVx32Pxo0jpUjHoGr0HJMHGZ8M%3D&token=%2Fs%2FcOiPbIzNdXQbLqZPDKmB02RANtTOkdwAPYI6vKjfUfuEQcHyroNRtyvL5lr5W>
| Approve sender
<https://www.boxbe.com/anno?tc_serial=61984809141&tc_rand=2014793862&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&key=JQ3tI3eduxxJHzt5mWVx32Pxo0jpUjHoGr0HJMHGZ8M%3D&token=%2Fs%2FcOiPbIzNdXQbLqZPDKmB02RANtTOkdwAPYI6vKjfUfuEQcHyroNRtyvL5lr5W>
| Approve domain
<https://www.boxbe.com/anno?tc_serial=61984809141&tc_rand=2014793862&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&&dom&key=JQ3tI3eduxxJHzt5mWVx32Pxo0jpUjHoGr0HJMHGZ8M%3D&token=%2Fs%2FcOiPbIzNdXQbLqZPDKmB02RANtTOkdwAPYI6vKjfUfuEQcHyroNRtyvL5lr5W>
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!