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

From Brad DeJong
Subject Re: Snapshot too old logging
Date
Msg-id F8F0ED16CB59F247B7EFD0E1DB34BC1F5CB570E3@USALWEXMBX3.infor.com
Whole thread Raw
In response to Re: Snapshot too old logging  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Nov 15, 2016 at 10:30 AM, Tom Lane wrote:
>
> Kevin Grittner <kgrittn@gmail.com> writes:
> > 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?
>
> > 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;
>
> Any such code is broken on its face because of localization.
> Perhaps including the relname in the main message would make it unduly
> long, but if not I'd vote for doing it that way.

+1 for relname in the main message.



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Snapshot too old logging
Next
From: Robert Haas
Date:
Subject: Re: Snapshot too old logging