mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-27 11:07:18 +02:00
ec0baf949e
reduce contention for the former single LockMgrLock. Per my recent proposal. I set it up for 16 partitions, but on a pgbench test this gives only a marginal further improvement over 4 partitions --- we need to test more scenarios to choose the number of partitions. |
||
|---|---|---|
| .. | ||
| ipc.c | ||
| ipci.c | ||
| Makefile | ||
| pmsignal.c | ||
| procarray.c | ||
| README | ||
| shmem.c | ||
| shmqueue.c | ||
| sinval.c | ||
| sinvaladt.c | ||
$PostgreSQL: pgsql/src/backend/storage/ipc/README,v 1.4 2003/11/29 19:51:56 pgsql 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.