| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Question about behavior of snapshot too old feature |
| Date: | 2016-10-19 16:11:38 |
| Message-ID: | 20161019161138.GK5087@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 19, 2016 at 11:08:28AM -0500, Kevin Grittner wrote:
> On Wed, Oct 19, 2016 at 10:04 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> > Slide 10 of this presentation has an example showing
> > old_snapshot_threshold set to '1min':
> >
> > http://momjian.us/main/writings/pgsql/features.pdf
>
> If the presentation is intending to show reasonable values for
> production use, that would be better as, maybe, '2h'.
>
> As the documentation says at:
>
> https://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-OLD-SNAPSHOT-THRESHOLD
The example is just to illustrate the activities required to trigger it,
e.g. pg_sleep(), VACUUM.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-10-19 16:14:50 | Portable check for unportable <ctype.h> macro usage |
| Previous Message | Kevin Grittner | 2016-10-19 16:08:28 | Re: Question about behavior of snapshot too old feature |