| From: | loganathan P <plogandba(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, loganathan P <plogandba(at)gmail(dot)com> |
| Subject: | Re: Application Error When Accessing the Table – PostgreSQL 15.18 |
| Date: | 2026-11-05 02:53:05 |
| Message-ID: | CAFX4Q9+K_2g+vQfsd0_5_orXpo40AwED-8bCoCoG34b78J+FQA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> [image: Boxbe] <https://www.boxbe.com/overview> Tom Lane (
> tgl(at)sss(dot)pgh(dot)pa(dot)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(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 | Igor Korot | 2026-11-05 02:56:25 | Re: Return trimmed string from the query |
| Previous Message | Tom Lane | 2026-11-04 15:03:54 | Re: Application Error When Accessing the Table – PostgreSQL 15.18 |