| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Kevin Grittner <kgrittn(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-committers(at)postgresql(dot)org" <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Date: | 2016-04-13 18:52:15 |
| Message-ID: | CACjxUsNvVsjJiFy=d2jXZYpo8Evq89YHVjFnLRv5fTF2F5OWPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Apr 13, 2016 at 12:25 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> [test results with old_snapshot_threshold = 0 and 10]
From the docs:
| A value of -1 disables this feature, and is the default.
> Yuck. Aside from the fact that performance tanks when the feature is
> turned on, it seems that there is a significant effect even with it
> turned off.
No evidence of that has been provided. -1 is off; 0 is for testing
very fast expiration.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-04-13 18:56:37 | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Previous Message | Andres Freund | 2016-04-13 18:20:19 | Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gianni Ceccarelli | 2016-04-13 18:54:56 | Re: sign function with INTERVAL? |
| Previous Message | Daniel Lenski | 2016-04-13 18:36:21 | sign function with INTERVAL? |