Re: [PATCH] Identify LWLocks in tracepoints

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Identify LWLocks in tracepoints
Date: 2021-05-03 19:06:30
Message-ID: 29620fc3-f99c-fd8d-9396-07836e070f04@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30.04.21 05:22, Craig Ringer wrote:
> On Thu, 29 Apr 2021 at 15:31, Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>> So if you could produce a separate patch that adds the
>>> _ENABLED guards targeting PG14 (and PG13), that would be helpful.
>>
>> Here is a proposed patch for this.
>
> LGTM.
>
> Applies and builds fine on master and (with default fuzz) on
> REL_13_STABLE. Works as expected.

committed

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-05-03 19:07:07 PG in container w/ pid namespace is init, process exits cause restart
Previous Message Matthias van de Meent 2021-05-03 19:06:19 Re: MaxOffsetNumber for Table AMs