mirror of
https://github.com/postgres/postgres.git
synced 2025-09-02 04:21:28 +03:00
Spelling adjustments
This commit is contained in:
@@ -1354,7 +1354,7 @@ WaitEventSetWaitBlock(WaitEventSet *set, int cur_timeout,
|
||||
* because we don't expect the pipe to become readable or to have
|
||||
* any errors either, treat those cases as postmaster death, too.
|
||||
*
|
||||
* Be paranoid about a spurious event signalling the postmaster as
|
||||
* Be paranoid about a spurious event signaling the postmaster as
|
||||
* being dead. There have been reports about that happening with
|
||||
* older primitives (select(2) to be specific), and a spurious
|
||||
* WL_POSTMASTER_DEATH event would be painful. Re-checking doesn't
|
||||
@@ -1613,7 +1613,7 @@ WaitEventSetWaitBlock(WaitEventSet *set, int cur_timeout,
|
||||
* we don't expect the pipe to become readable or to have any
|
||||
* errors either, treat those cases as postmaster death, too.
|
||||
*
|
||||
* Be paranoid about a spurious event signalling the postmaster as
|
||||
* Be paranoid about a spurious event signaling the postmaster as
|
||||
* being dead. There have been reports about that happening with
|
||||
* older primitives (select(2) to be specific), and a spurious
|
||||
* WL_POSTMASTER_DEATH event would be painful. Re-checking doesn't
|
||||
|
@@ -1,7 +1,7 @@
|
||||
/*-------------------------------------------------------------------------
|
||||
*
|
||||
* procsignal.c
|
||||
* Routines for interprocess signalling
|
||||
* Routines for interprocess signaling
|
||||
*
|
||||
*
|
||||
* Portions Copyright (c) 1996-2020, PostgreSQL Global Development Group
|
||||
@@ -30,7 +30,7 @@
|
||||
#include "tcop/tcopprot.h"
|
||||
|
||||
/*
|
||||
* The SIGUSR1 signal is multiplexed to support signalling multiple event
|
||||
* The SIGUSR1 signal is multiplexed to support signaling multiple event
|
||||
* types. The specific reason is communicated via flags in shared memory.
|
||||
* We keep a boolean flag for each possible "reason", so that different
|
||||
* reasons can be signaled to a process concurrently. (However, if the same
|
||||
@@ -40,8 +40,8 @@
|
||||
* Each process that wants to receive signals registers its process ID
|
||||
* in the ProcSignalSlots array. The array is indexed by backend ID to make
|
||||
* slot allocation simple, and to avoid having to search the array when you
|
||||
* know the backend ID of the process you're signalling. (We do support
|
||||
* signalling without backend ID, but it's a bit less efficient.)
|
||||
* know the backend ID of the process you're signaling. (We do support
|
||||
* signaling without backend ID, but it's a bit less efficient.)
|
||||
*
|
||||
* The flags are actually declared as "volatile sig_atomic_t" for maximum
|
||||
* portability. This should ensure that loads and stores of the flag
|
||||
@@ -420,7 +420,7 @@ WaitForProcSignalBarrier(uint64 generation)
|
||||
/*
|
||||
* Perform global barrier related interrupt checking.
|
||||
*
|
||||
* Any backend that participates in ProcSignal signalling must arrange to
|
||||
* Any backend that participates in ProcSignal signaling must arrange to
|
||||
* call this function periodically. It is called from CHECK_FOR_INTERRUPTS(),
|
||||
* which is enough for normal backends, but not necessarily for all types of
|
||||
* background processes.
|
||||
|
@@ -1182,7 +1182,7 @@ shm_mq_wait_internal(shm_mq *mq, PGPROC **ptr, BackgroundWorkerHandle *handle)
|
||||
}
|
||||
}
|
||||
|
||||
/* Wait to be signalled. */
|
||||
/* Wait to be signaled. */
|
||||
(void) WaitLatch(MyLatch, WL_LATCH_SET | WL_EXIT_ON_PM_DEATH, 0,
|
||||
WAIT_EVENT_MQ_INTERNAL);
|
||||
|
||||
|
@@ -1,7 +1,7 @@
|
||||
/*-------------------------------------------------------------------------
|
||||
*
|
||||
* signalfuncs.c
|
||||
* Functions for signalling backends
|
||||
* Functions for signaling backends
|
||||
*
|
||||
* Portions Copyright (c) 1996-2020, PostgreSQL Global Development Group
|
||||
* Portions Copyright (c) 1994, Regents of the University of California
|
||||
|
@@ -92,7 +92,7 @@ InitRecoveryTransactionEnvironment(void)
|
||||
/*
|
||||
* Initialize shared invalidation management for Startup process, being
|
||||
* careful to register ourselves as a sendOnly process so we don't need to
|
||||
* read messages, nor will we get signalled when the queue starts filling
|
||||
* read messages, nor will we get signaled when the queue starts filling
|
||||
* up.
|
||||
*/
|
||||
SharedInvalBackendInit(true);
|
||||
|
@@ -759,7 +759,7 @@ LockAcquire(const LOCKTAG *locktag,
|
||||
* reportMemoryError specifies whether a lock request that fills the lock
|
||||
* table should generate an ERROR or not. Passing "false" allows the caller
|
||||
* to attempt to recover from lock-table-full situations, perhaps by forcibly
|
||||
* cancelling other lock holders and then retrying. Note, however, that the
|
||||
* canceling other lock holders and then retrying. Note, however, that the
|
||||
* return code for that is LOCKACQUIRE_NOT_AVAIL, so that it's unsafe to use
|
||||
* in combination with dontWait = true, as the cause of failure couldn't be
|
||||
* distinguished.
|
||||
|
Reference in New Issue
Block a user