| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)gmail(dot)com>, Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold < |
| Date: | 2016-05-03 15:39:54 |
| Message-ID: | 20160503153954.uaziygevty6st3dz@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2016-05-02 10:32:28 -0400, Robert Haas wrote:
> You are certainly welcome to add a new open item to cover those
> complaints.
Done that.
> But I do not want to blur together the discussion of
> whether the feature is well-designed with the question of whether it
> regresses performance when it is turned off. Those are severable
> issues, meriting separate discussion (and probably separate threads).
The current thread already contains a lot of information about both, so
separating doesn't seem beneficial.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-03 18:45:42 | pgsql: Fix more things to be parallel-safe. |
| Previous Message | Robert Haas | 2016-05-03 15:01:17 | pgsql: Tweak a few more things in preparation for upcoming pgindent run |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2016-05-03 15:45:05 | Re: old_snapshot_threshold's interaction with hash index |
| Previous Message | Tom Lane | 2016-05-03 15:36:39 | Re: pgindent fixups |