Skip site navigation (1) Skip section navigation (2)

pgsql/src/backend/storage/buffer (bufmgr.c)

From: tgl(at)postgresql(dot)org
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql/src/backend/storage/buffer (bufmgr.c)
Date: 2001-01-12 21:53:58
Message-ID: 200101122153.f0CLrw892811@hub.org (view raw or flat)
Thread:
Lists: pgsql-committers
  Date: Friday, January 12, 2001 @ 16:53:57
Author: tgl

Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/storage/buffer
     from hub.org:/home/projects/pgsql/tmp/cvs-serv92773/src/backend/storage/buffer

Modified Files:
	bufmgr.c 

-----------------------------  Log Message  -----------------------------

Add more critical-section calls: all code sections that hold spinlocks
are now critical sections, so as to ensure die() won't interrupt us while
we are munging shared-memory data structures.  Avoid insecure intermediate
states in some code that proc_exit will call, like palloc/pfree.  Rename
START/END_CRIT_CODE to START/END_CRIT_SECTION, since that seems to be
what people tend to call them anyway, and make them be called with () like
a function call, in hopes of not confusing pg_indent.
I doubt that this is sufficient to make SIGTERM safe anywhere; there's
just too much code that could get invoked during proc_exit().


pgsql-committers by date

Next:From: tglDate: 2001-01-12 21:53:59
Subject: pgsql/src/backend/storage/lmgr (proc.c)
Previous:From: tglDate: 2001-01-12 21:53:57
Subject: pgsql/src/backend/commands (sequence.c vacuum.c)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group