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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Oskari Saarenmaa <os(at)ohmu(dot)fi>
Cc: 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-01-05 17:23:18
Message-ID: 20150105172318.GM1457@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
optimize-locking-locked-multi-5.patch text/x-diff 24.1 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2015-01-05 17:45:05 Re: BUG #12428: Incorrect Code
Previous Message honey 2015-01-05 12:47:27 BUG #12428: Incorrect Code