From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Move lwlock-release probe back where it belongs |
Date: | 2021-03-21 07:12:36 |
Message-ID: | E1lNsGK-0001Rc-S8@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Move lwlock-release probe back where it belongs
The documentation specifically states that lwlock-release fires before
any released waiters have been awakened. It worked that way until
ab5194e6f617a9a9e7aadb3dd1cee948a42d0755, where is seems to have been
misplaced accidentally. Move it back where it belongs.
Author: Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>
Discussion: https://www.postgresql.org/message-id/CAGRY4nwxKUS_RvXFW-ugrZBYxPFFM5kjwKT5O+0+Stuga5b4+Q@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/96ae658e6238c5e69819fb1557c2c14a555506d8
Modified Files
--------------
src/backend/storage/lmgr/lwlock.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-03-21 15:50:49 | pgsql: Suppress various new compiler warnings. |
Previous Message | Tomas Vondra | 2021-03-20 23:29:17 | pgsql: Use valid compression method in brin_form_tuple |