Re: Snapshot too old logging

From: Brad DeJong <Brad(dot)Dejong(at)infor(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Snapshot too old logging
Date: 2016-11-15 18:23:26
Message-ID: F8F0ED16CB59F247B7EFD0E1DB34BC1F5CB570E3@USALWEXMBX3.infor.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 15, 2016 at 10:30 AM, Tom Lane wrote:
>
> Kevin Grittner <kgrittn(at)gmail(dot)com> writes:
> > On Tue, Nov 15, 2016 at 3:38 AM, Magnus Hagander <magnus(at)hagander(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-11-15 18:27:28 Re: Snapshot too old logging
Previous Message Magnus Hagander 2016-11-15 18:18:27 Re: Snapshot too old logging