mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-27 11:47:19 +02:00
624292aa35
memory say 'out of shared memory'; some were doing that and some just said 'out of memory'. Also add a HINT about increasing max_locks_per_transaction where relevant, per suggestion from Sean Chittenden. (The former change does not break the strings freeze; the latter does, but I think it's worth doing anyway.) |
||
|---|---|---|
| .. | ||
| ipc.c | ||
| ipci.c | ||
| Makefile | ||
| pmsignal.c | ||
| README | ||
| shmem.c | ||
| shmqueue.c | ||
| sinval.c | ||
| sinvaladt.c | ||
$Header: /cvsroot/pgsql/src/backend/storage/ipc/README,v 1.3 2003/07/24 22:04:09 tgl Exp $ Mon Jul 18 11:09:22 PDT 1988 W.KLAS Cache invalidation synchronization routines: =========================================== 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.