On Wed, Mar 30, 2016 at 2:34 PM, Kevin Grittner <kgri...@gmail.com> wrote:
> A connection should not get the > error just because it is using a snapshot that tries to look at > data that might be wrong, and the connection holding the long-lived > snapshot doesn't do that until it awakes from the sleep and runs > the next SELECT command. Well, that came out wrong. A connection should not get the "snapshot too old" error just because it is *holds* an old snapshot; it must actually attempt to read an affected page *using* an old snapshot, and the connection holding the long-lived snapshot doesn't do that until it awakes from the sleep and runs the next SELECT command. Sorry for any confusion from the sloppy editing. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
