Re: Broken handling of lwlocknames.h - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Broken handling of lwlocknames.h
Date
Msg-id CA+TgmoZYCadeCwOC51bS-VSobDiTDd+e0rk0oMCRrxs0WDKjig@mail.gmail.com
Whole thread Raw
In response to Re: Broken handling of lwlocknames.h  (Noah Misch <noah@leadboat.com>)
Responses Re: Broken handling of lwlocknames.h  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jul 1, 2016 at 12:09 AM, Noah Misch <noah@leadboat.com> wrote:
> [Action required within 72 hours.  This is a generic notification.]
>
> The above-described topic is currently a PostgreSQL 9.6 open item.  Robert,
> since you committed the patch believed to have created it, you own this open
> item.  If some other commit is more relevant or if this does not belong as a
> 9.6 open item, please let us know.  Otherwise, please observe the policy on
> open item ownership[1] and send a status update within 72 hours of this
> message.  Include a date for your subsequent status update.  Testers may
> discover new open items at any time, and I want to plan to get them all fixed
> well in advance of shipping 9.6rc1.  Consequently, I will appreciate your
> efforts toward speedy resolution.  Thanks.
>
> [1] http://www.postgresql.org/message-id/20160527025039.GA447393@tornado.leadboat.com

Since Tom proposed the approach which Michael's patch takes, I'm
hoping he will review and commit this.  If it is left to me to fix it,
I may just adopt a minimal fix.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [sqlsmith] crashes in RestoreSnapshot on hot standby
Next
From: Robert Haas
Date:
Subject: Re: Bug in batch tuplesort memory CLUSTER case (9.6 only)