pgsql: Add comment to explain why PGReserveSemaphores() is called early - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Add comment to explain why PGReserveSemaphores() is called early
Date
Msg-id E1vGzNS-005IKt-0f@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Add comment to explain why PGReserveSemaphores() is called early

Before commit e25626677f, PGReserveSemaphores() had to be called
before SpinlockSemaInit() because spinlocks were implemented using
semaphores on some platforms (--disable-spinlocks). Add a comment
explaining that.

Author: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Discussion: https://www.postgresql.org/message-id/CAExHW5seSZpPx-znjidVZNzdagGHOk06F+Ds88MpPUbxd1kTaA@mail.gmail.com
Backpatch-to: 18

Branch
------
REL_18_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/75ec47c38bcf8777164cf91885eb907eb3fc369b

Modified Files
--------------
src/backend/storage/ipc/ipci.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Fix redundancy in error message
Next
From: Álvaro Herrera
Date:
Subject: Re: pgsql: pg_createsubscriber: Fix error complaining about the wrong thing