pgsql: Better internal documentation of locking for Hot Standby conflict - Mailing list pgsql-committers

From sriggs@postgresql.org (Simon Riggs)
Subject pgsql: Better internal documentation of locking for Hot Standby conflict
Date
Msg-id 20100121005358.9E9757541B9@cvs.postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Well, the systemtap guys moved the goalposts again: with the
Next
From: Robert Haas
Date:
Subject: Re: pgsql: Write a WAL record whenever we perform an operation without