pgsql: Fix LWLockAssign() so that it can safely be executed after - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Fix LWLockAssign() so that it can safely be executed after
Date
Msg-id 20051007214239.779EEDA583@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix LWLockAssign() so that it can safely be executed after postmaster
initialization.  Add spinlocking, fix EXEC_BACKEND unsafeness.

Modified Files:
--------------
    pgsql/src/backend/storage/ipc:
        shmem.c (r1.85 -> r1.86)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/shmem.c.diff?r1=1.85&r2=1.86)
    pgsql/src/backend/storage/lmgr:
        lwlock.c (r1.31 -> r1.32)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lwlock.c.diff?r1=1.31&r2=1.32)

pgsql-committers by date:

Previous
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Minor parentheses cleanup.
Next
From: aglio@pgfoundry.org (User Aglio)
Date:
Subject: press - pr: Extended the "licensing" paragraph to be more pointed.