Re: Improve LWLock tranche name visibility across backends

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Rahila Syed <rahilasyed90(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve LWLock tranche name visibility across backends
Date: 2025-08-08 18:09:29
Message-ID: CAA5RZ0tQ+EYSTOd2hQ8RXdsNfGBLAtOe-YmnsTE6ZVg0E-4qew@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From this discussion, and the fact that the tranche name could come from
either local or shared memory, I think we should have tests.
So, I am working on adding tests using INJECTION_POINTS.

Some of the tests I have in mind now are:

1/ Does the shared memory grow correctly,
2/ Is the tranche name being returned the correct one
3/ Is the local cache being updated correctly.

I will have an updated patch with the new test
module early next week.

--
Sami

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zaeem Hussain 2025-08-08 18:19:18 Granulaur spinlock wait events
Previous Message Tom Lane 2025-08-08 17:50:30 First-draft back-branch release notes are up