pgsql: lwlock: Remove support for disowned lwlwocks - Mailing list pgsql-committers

From Andres Freund
Subject pgsql: lwlock: Remove support for disowned lwlwocks
Date
Msg-id E1vgTVA-000fhX-39@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
lwlock: Remove support for disowned lwlwocks

This reverts commit f8d7f29b3e81db59b95e4b5baaa6943178c89fd8, plus parts of
subsequent commits fixing a typo in a parameter name.

Support for disowned lwlocks was added for the benefit of AIO, to be able to
have content locks "owned" by the AIO subsystem. But as of commit fcb9c977aa5,
content locks do not use lwlocks anymore.

It does not seem particularly likely that we need this facility outside of the
AIO use-case, therefore remove the now unused functions.

I did choose to keep the comment added in the aforementioned commit about
lock->owner intentionally being left pointing to the last owner.

Reviewed-by: Chao Li <li.evan.chao@gmail.com>
Discussion: https://postgr.es/m/cj5mcjdpucvw4a54hehslr3ctukavrbnxltvuzzhqnimvpju5e@cy3g3mnsefwz

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/d40fd85187d06f7bd16fb4d0067bad0b1d248718

Modified Files
--------------
src/backend/storage/lmgr/lwlock.c | 71 ++++-----------------------------------
src/include/storage/lwlock.h      |  2 --
2 files changed, 6 insertions(+), 67 deletions(-)


pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: pgsql: bufmgr: Implement buffer content locks independently of lwlocks
Next
From: Michael Paquier
Date:
Subject: pgsql: Add pg_clear_extended_stats()