Tom Lane d3fc362ec2 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.)		2001-12-28 18:16:43 +00:00
..
buffer	Clean up usage-statistics display code (ShowUsage and friends). StatFp	2001-11-10 23:51:14 +00:00
file	New pgindent run with fixes suggested by Tom. Patch manually reviewed,	2001-11-05 17:46:40 +00:00
freespace	New pgindent run with fixes suggested by Tom. Patch manually reviewed,	2001-11-05 17:46:40 +00:00
ipc	Ensure that all direct uses of spinlock-protected data structures use	2001-12-28 18:16:43 +00:00
large_object	pgindent run on all C files. Java run to follow. initdb/regression	2001-10-25 05:50:21 +00:00
lmgr	Ensure that all direct uses of spinlock-protected data structures use	2001-12-28 18:16:43 +00:00
page	Add casts to suppress compiler warnings observed on Darwin platform	2001-11-08 04:05:13 +00:00
smgr	New pgindent run with fixes suggested by Tom. Patch manually reviewed,	2001-11-05 17:46:40 +00:00
Makefile	Install infrastructure for shared-memory free space map. Doesn't actually	2001-06-27 23:31:40 +00:00