mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-27 09:47:18 +02:00
f9ed327f76
MaxStandbyDelay. Use the GUC units mechanism for the value, and choose more appropriate timestamp functions for performing tests with it. Make the ps_activity manipulation in ResolveRecoveryConflictWithVirtualXIDs have behavior similar to ps_activity code elsewhere, notably not updating the display when update_process_title is off and not truncating the display contents at an arbitrarily-chosen length. Improve the docs to be explicit about what MaxStandbyDelay actually measures, viz the difference between primary and standby servers' clocks, and the possible hazards if their clocks aren't in sync. |
||
|---|---|---|
| .. | ||
| ipc.c | ||
| ipci.c | ||
| Makefile | ||
| pmsignal.c | ||
| procarray.c | ||
| procsignal.c | ||
| README | ||
| shmem.c | ||
| shmqueue.c | ||
| sinval.c | ||
| sinvaladt.c | ||
| standby.c | ||
$PostgreSQL: pgsql/src/backend/storage/ipc/README,v 1.5 2008/03/20 17:55:15 momjian Exp $ 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.