Re: reporting TID/table with corruption error - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: reporting TID/table with corruption error
Date
Msg-id CAH2-WzmCLNK09r_C+A9ZxmmdZ2AjgDGyCJjVYWBun2LUws_gJw@mail.gmail.com
Whole thread Raw
In response to reporting TID/table with corruption error  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: reporting TID/table with corruption error  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers
On Thu, Aug 19, 2021 at 9:38 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> A customer recently hit this error message:
>
> ERROR:  t_xmin is uncommitted in tuple to be updated
>
> This was not very informative, so without any clues, we had to let it
> go.  But it did occur to me that we can improve this message so that we
> know details such as the TID and the relation that caused the issue, so
> that if it ever occurs again we can at least look at the WAL stream for
> anything affecting the tuple, maybe it'd help to understand the problem.

I think that this is a very good idea. Ideally this stuff would be
more standardized.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Jesper Pedersen
Date:
Subject: Re: Middleware Messages for FE/BE
Next
From: Sadhuprasad Patro
Date:
Subject: Re: Support reset of Shared objects statistics in "pg_stat_reset" function