pgsql: Better internal documentation of locking for Hot Standby conflict

From: sriggs(at)postgresql(dot)org (Simon Riggs)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Better internal documentation of locking for Hot Standby conflict
Date: 2010-01-21 00:53:58
Message-ID: 20100121005358.9E9757541B9@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Better internal documentation of locking for Hot Standby conflict resolution.
Discuss the reasons for the lock type we hold on ProcArrayLock while deriving
the conflict list. Cover the idea of false positive conflicts and seemingly
strange effects on snapshot derivation.

Modified Files:
--------------
pgsql/src/backend/storage/ipc:
procarray.c (r1.57 -> r1.58)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/procarray.c?r1=1.57&r2=1.58)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2010-01-21 03:40:05 Re: pgsql: Write a WAL record whenever we perform an operation without
Previous Message Tom Lane 2010-01-20 23:12:15 pgsql: Well, the systemtap guys moved the goalposts again: with the