Re: [PATCH] Identify LWLocks in tracepoints

Craig Ringer <craig.ringer@enterprisedb.com>

From: Craig Ringer <craig.ringer@enterprisedb.com>

To: david@pgmasters.net

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>

Date: 2021-03-10T05:38:06Z

Lists: pgsql-hackers

Attachments

0001-Pass-the-target-LWLock-and-tranche-ID-to-LWLock-trac.patch (text/x-patch) patch 0001
0004-SDT-tracepoints-for-backend-type-and-postmaster-pid-.patch (text/x-patch) patch 0004
0003-Comments-on-LWLock-tranches.patch (text/x-patch) patch 0003
0002-Add-to-the-tracepoints-in-LWLock-routines.patch (text/x-patch) patch 0002

On Wed, 3 Mar 2021 at 20:50, David Steele <david@pgmasters.net> wrote:

> On 1/22/21 6:02 AM, Peter Eisentraut wrote:
>
> This patch set no longer applies:
> http://cfbot.cputube.org/patch_32_2927.log.
>
> Can we get a rebase? Also marked Waiting on Author.
>

Rebased as requested.

I'm still interested in whether Andres will be able to do anything about
identifying LWLocks in a cross-backend manner. But this work doesn't really
depend on that; it'd benefit from it, but would be easily adapted to it
later if needed.

Commits

Emit dummy statements for probes.d probes when disabled
- 0d204a4b09f7 13.3 landed
- fa8fbadb934b 14.0 landed
Prevent lwlock dtrace probes from unnecessary work
- e48ce7ef0ef8 13.3 landed
- b94409a02f61 14.0 landed
doc: Fix typo in logicaldecoding.sgml.
- 5fe83adad9ef 14.0 cited
Move lwlock-release probe back where it belongs
- 96ae658e6238 14.0 landed
Remove bogus tracepoint
- 09418bed67a7 14.0 landed
Simplify LWLock tranche machinery by removing array_base/array_stride.
- 3761fe3c20bb 10.0 cited
Improve LWLock scalability.
- ab5194e6f617 9.5.0 cited