Re: old_snapshot_threshold documentation

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: old_snapshot_threshold documentation
Date: 2016-08-30 11:44:19
Message-ID: CACjxUsNuFP0kUGn2rzj=NMXOODFL80wGqtaN=GmARwVsdQVHeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 26, 2016 at 1:34 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> I doubt the documentation for old_snapshot_threshold is going to be
> understood by many ordinary users. What is a "snapshot", first of all?
> Why would a snapshot be old? Why is that a problem? What can I do to
> avoid it? What are the circumstances in practice where this issue would
> arise, and what are the trade-offs? Where can I see existing snapshots
> and how old they are?

I'll put something together to improve that. I think largely that
will consist of references to other sections of the documentation,
like MVCC, vacuuming, pg_stat_activity, etc.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-08-30 12:18:37 Re: 9.5.4: Segfault (signal 11) while running ALTER TABLE
Previous Message Tom Lane 2016-08-30 11:39:16 Re: Postgres abort found in 9.3.11