pgsql: Assorted code review for recent ProcArrayLock patch.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Assorted code review for recent ProcArrayLock patch.
Date: 2015-09-03 17:35:55
Message-ID: E1ZXYQV-00011K-H2@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Assorted code review for recent ProcArrayLock patch.

Post-commit review by Andres Freund discovered a couple of concurrency
bugs in the original patch: specifically, if the leader cleared a
follower's XID before it reached PGSemaphoreLock, the semaphore would be
left in the wrong state; and if another process did PGSemaphoreUnlock
for some unrelated reason, we might resume execution before the fact
that our XID was cleared was globally visible.

Also, improve the wording of some comments, rename nextClearXidElem
to firstClearXidElem in PROC_HDR for clarity, and drop some volatile
qualifiers that aren't necessary.

Amit Kapila, reviewed and slightly revised by me.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/4aec49899e5782247e134f94ce1c6ee926f88e1c

Modified Files
--------------
src/backend/storage/ipc/procarray.c | 41 +++++++++++++++++++++++++----------
src/backend/storage/lmgr/proc.c | 3 ++-
src/include/storage/proc.h | 5 +++--
3 files changed, 34 insertions(+), 15 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Kapila 2015-09-04 07:48:54 Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file
Previous Message Fujii Masao 2015-09-03 13:31:33 pgsql: Document that max_worker_processes must be high enough in standb