Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated.
Date: 2016-08-29 22:13:00
Message-ID: 20160829221300.GA435142@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas wrote:

> That would also have the advantage of improving the test coverage for
> pg_stat_statements, which is at the moment quite a bit thinner than
> the coverage for lwlock.c.

Hmm, the coverage-html report is not currently covering contrib ... I
suppose that's an easily fixable oversight.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2016-08-30 00:26:56 Re: OpenSSL 1.1 breaks configure and more
Previous Message Alvaro Herrera 2016-08-29 22:10:41 Re: Write Ahead Logging for Hash Indexes

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Kapila 2016-08-30 02:27:19 Re: Re: [COMMITTERS] pgsql: Change the way that LWLocks for extensions are allocated.
Previous Message Alvaro Herrera 2016-08-29 22:01:53 pgsql: Split hash.h hash_xlog.h