Horton

Re: reporting TID/table with corruption error

Peter Geoghegan <pg@bowt.ie>

View thread View on postgr.es
From: Peter Geoghegan <pg@bowt.ie>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-19T16:44:09Z
Lists: 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

Commits

  1. Report tuple address in data-corruption error message