reporting TID/table with corruption error
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-19T16:37:58Z
Lists: pgsql-hackers
Attachments
- report-tuple.patch (text/x-diff) patch
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. So I propose the following patch. -- Álvaro Herrera
Commits
-
Report tuple address in data-corruption error message
- fa8ae19bea7f 12.9 landed
- eae08e21653c 14.0 landed
- 961dd7565726 15.0 landed
- 6197d7b5383e 13.5 landed
- 37e4682520db 9.6.24 landed
- 02797ffa9a31 10.19 landed
- 0105b7aaa3f4 11.14 landed