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

From Kevin Grittner
Subject Re: Snapshot too old logging
Date
Msg-id CACjxUsNCUYw85x_fApS4JMOdMvFU0cU-d=Quq_HLi7t4wy8ctw@mail.gmail.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 12:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> Is there value in showing which snapshot as well? Something like:
>> DETAIL: snapshot <xyz> is too old to access relation <relation>
>
> Snapshots don't have names, and I can't think of a useful way of
> identifying them to users.

The time that the snapshot was taken might be useful; I can't think
of anything else that would be.  The main thing would be to include
the relation, with an indication that it's not necessarily true
that access to *any* part of the relation would be a problem.
Mentioning the block number would tend to support that idea, and
might be of some use.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Snapshot too old logging
Next
From: Magnus Hagander
Date:
Subject: Re: Snapshot too old logging