Horton
Menu

Re: Adding locks statistics

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Jeff Davis <pgsql@j-davis.com>, Greg Sabino Mullane <htamfids@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-03-25T05:25:01Z
Lists: pgsql-hackers 
On Wed, Mar 25, 2026 at 03:15:19AM +0000, Bertrand Drouvot wrote:
> Thanks for the test removal. I created an open item for v19 so that we
> don't forget to re-add a new version of the tests. I'll work on it.
> 
> [1]: https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items

Thanks for adding that.  We are most likely going to need the help of
the CI here.  The buildfarm has been fortunately (unfortunately?)
stable on this one, and that would make for less noise overall.
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix injection point detach timing problem in TAP test for lock stats

  2. Use single LWLock for lock statistics in pgstats

  3. Add tests for lock statistics, take two

  4. Remove isolation test lock-stats

  5. Avoid including clog.h in proc.h

  6. Don't include storage/lock.h in so many headers

  7. Add support for lock statistics in pgstats

  8. Move some code blocks in lock.c and proc.c

  9. Move declarations related to locktags from lock.h to new locktag.h