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

From Brad DeJong
Subject Re: Snapshot too old logging
Date
Msg-id F8F0ED16CB59F247B7EFD0E1DB34BC1F5CB5712C@USALWEXMBX3.infor.com
Whole thread Raw
In response to Re: Snapshot too old logging  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">On Tue,
Nov15, 2016 at 12:20 PM Magnus Hagander wrote:</span><p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">>Is there value in showing the snapshot as well?</span><p
class="MsoNormal"><spanstyle="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Idon't think so. Knowing the relname let's you look at your
report/joband figure out if the access to that relation can be moved. Having the exact snapshot version isn't going to
changethat. And if you're doing auto-retry, you probably only care if it is happening on the same relation
consistently.</span></div>

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Snapshot too old logging
Next
From: Robert Haas
Date:
Subject: Re: Password identifiers, protocol aging and SCRAM protocol