Re: Exposing the lock manager's WaitForLockers() to SQL

From: Will Mortensen <will(at)extrahop(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Marco Slot <marco(dot)slot(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, marco(at)citusdata(dot)com, Yvonne Chen <yvonne(at)extrahop(dot)com>, Jacob Speidel <jacob(at)extrahop(dot)com>
Subject: Re: Exposing the lock manager's WaitForLockers() to SQL
Date: 2024-01-06 10:57:04
Message-ID: CAMpnoC62nUjMqzjkvCq90TCFOqptHZyy6rhT_j_NASeaU+Q1+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simplified the code and docs, and rewrote the example with more prose
instead of PL/pgSQL, which unfortunately made it longer, although it
could be truncated. Not really sure what's best...

Attachment Content-Type Size
v5-0001-Refactor-GetLockConflicts-into-more-general-GetLo.patch application/octet-stream 8.1 KB
v5-0003-Add-WAIT-FOR-LOCKERS-command.patch application/octet-stream 42.5 KB
v5-0002-Allow-specifying-single-lockmode-in-WaitForLocker.patch application/octet-stream 8.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2024-01-06 12:00:08 Re: Exposing the lock manager's WaitForLockers() to SQL
Previous Message Alexander Cheshev 2024-01-06 09:08:23 Re: Multidimensional Histograms