pgsql/src/backend access/transam/xlog.c storag ...

From: tgl(at)postgresql(dot)org
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql/src/backend access/transam/xlog.c storag ...
Date: 2001-12-28 18:16:44
Message-ID: 200112281816.fBSIGiY09361@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

CVSROOT: /cvsroot
Module name: pgsql
Changes by: tgl(at)postgresql(dot)org 01/12/28 13:16:43

Modified files:
src/backend/access/transam: xlog.c
src/backend/storage/ipc: shmem.c
src/backend/storage/lmgr: proc.c

Log message:
Ensure that all direct uses of spinlock-protected data structures use
'volatile' pointers to access those structures, so that optimizing
compilers will not decide to move the structure accesses outside of the
spinlock-acquire-to-spinlock-release sequence. There are no known bugs
in these uses at present, but based on bad experience with lwlock.c,
it seems prudent to ensure that we protect these other uses too.
Per pghackers discussion around 12-Dec. (Note: it should not be
necessary to worry about structures protected by LWLocks, since the
LWLock acquire and release operations are not inline macros.)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2001-12-28 18:30:29 Re: pgsql/src/backend/postmaster postmaster.c
Previous Message momjian 2001-12-28 05:26:26 pgsql/doc TODO