| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: reporting TID/table with corruption error |
| Date: | 2021-08-19 16:44:09 |
| Message-ID: | CAH2-WzmCLNK09r_C+A9ZxmmdZ2AjgDGyCJjVYWBun2LUws_gJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 19, 2021 at 9:38 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sadhuprasad Patro | 2021-08-19 16:54:06 | Re: Support reset of Shared objects statistics in "pg_stat_reset" function |
| Previous Message | Jesper Pedersen | 2021-08-19 16:42:14 | Re: Middleware Messages for FE/BE |