rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-08-27 09:47:18 +02:00
Code Issues Packages Projects Releases Wiki Activity
ac36e6f71f
postgresql/src/backend/storage/ipc
History
Tom Lane ac36e6f71f Move CheckRecoveryConflictDeadlock() call to a safer place. 
This kluge was inserted in a spot apparently chosen at random: the lock
manager's state is not yet fully set up for the wait, and in particular
LockWaitCancel hasn't been armed by setting lockAwaited, so the ProcLock
will not get cleaned up if the ereport is thrown.  This seems to not cause
any observable problem in trivial test cases, because LockReleaseAll will
silently clean up the debris; but I was able to cause failures with tests
involving subtransactions.

Fixes breakage induced by commit c85c941470.
Back-patch to all affected branches.
2011-08-02 15:16:29 -04:00
..
ipc.c Stamp copyrights for year 2011. 2011-01-01 13:18:15 -05:00
ipci.c Implement genuine serializable isolation level. 2011-02-08 00:09:08 +02:00
Makefile Remove cvs keywords from all files. 2010-09-20 22:08:53 +02:00
pmsignal.c Introduce a pipe between postmaster and each backend, which can be used to 2011-07-08 18:44:07 +03:00
procarray.c pgindent run before PG 9.1 beta 1. 2011-04-10 11:42:00 -04:00
procsignal.c Stamp copyrights for year 2011. 2011-01-01 13:18:15 -05:00
README Remove useless whitespace at end of lines 2010-11-23 22:34:55 +02:00
shmem.c Implement genuine serializable isolation level. 2011-02-08 00:09:08 +02:00
shmqueue.c Minor sync rep corrections. 2011-03-10 14:57:02 -05:00
sinval.c Try to acquire relation locks in RangeVarGetRelid. 2011-07-08 22:19:30 -04:00
sinvaladt.c Minor stylistic corrections. 2011-08-01 08:24:45 -04:00
standby.c Move CheckRecoveryConflictDeadlock() call to a safer place. 2011-08-02 15:16:29 -04:00

README 

src/backend/storage/ipc/README

Cache Invalidation Synchronization Routines
===========================================

Mon Jul 18 11:09:22 PDT 1988  W.KLAS

The cache synchronization is done using a message queue. Every
backend can register a message which then has to be read by
all backends. A message read by all backends is removed from the
queue automatically. If a message has been lost because the buffer
was full, all backends that haven't read this message will be
told that they have to reset their cache state. This is done
at the time when they try to read the message queue.

The message queue is implemented as a shared buffer segment. Actually,
the queue is a circle to allow fast inserting, reading (invalidate data) and
maintaining the buffer.