Re: BUG #8470: 9.3 locking/subtransaction performance regression

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Oskari Saarenmaa <os(at)ohmu(dot)fi>, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8470: 9.3 locking/subtransaction performance regression
Date: 2015-04-02 00:56:16
Message-ID: 20150402005616.GB29404@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jan 5, 2015 at 02:23:18PM -0300, Alvaro Herrera wrote:
> I just got around to merging this patch to 9.5 sources. I'm glad I
> did it because in the course of doing so I noticed a bug in a recent
> patch, which led to commit d5e3d1e969d2f65009f718d3100d6565f47f9112
> (back-patched to 9.3).
>
> I'm now more confident in this code and will probably push this a few
> days, but only to 9.5 at least for now. It probably won't apply cleanly
> to 9.3 due to other changes in the area, such as 05315498012530d44cd89a2
> and df630b0dd5ea2de52972d456f5978a012436115e and others.

Where are we on this?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2015-04-02 02:01:45 Re: BUG #12462: NULLIF changes the argument type
Previous Message Bruce Momjian 2015-04-02 00:50:25 Re: 9.4 and reproducible "ERROR: could not read block 0 in file..."