Re: Snapshot too old logging - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Snapshot too old logging
Date
Msg-id CACjxUsNpNWoumWMxR9ppPNkvOHib406TkorkfMerDv2rLm0Mbw@mail.gmail.com
Whole thread Raw
In response to Snapshot too old logging  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Snapshot too old logging  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Nov 15, 2016 at 3:38 AM, Magnus Hagander <magnus@hagander.net> wrote:
> Is there a reason why we don't log which relation triggered the snapshot too
> old error when it happens?
>
> Since we do have Relation available in TestForOldSnapshot_impl(), shouldn't
> we be able to include it?
>
> Having that in the log message would be very helpful, but is there a reason
> why it wouldn't work?

I would probably not want to mess with the text of the error
itself, in case any client-side software bases recovery on that
rather than the SQLSTATE value; but including relation (and maybe
the timestamp on the snapshot?) in detail or context portions seems
like a great idea.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: jsonb_delete with arrays
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: psql \setfileref