mirror of
https://github.com/postgres/postgres.git
synced 2025-09-03 15:22:11 +03:00
Fix inconsistencies and typos in the tree
This is numbered take 8, and addresses again a set of issues with code comments, variable names and unreferenced variables. Author: Alexander Lakhin Discussion: https://postgr.es/m/b137b5eb-9c95-9c2f-586e-38aba7d59788@gmail.com
This commit is contained in:
@@ -3169,7 +3169,7 @@ DisplayXidCache(void)
|
||||
*
|
||||
* When we throw away subXIDs from KnownAssignedXids, we need to keep track of
|
||||
* that, similarly to tracking overflow of a PGPROC's subxids array. We do
|
||||
* that by remembering the lastOverflowedXID, ie the last thrown-away subXID.
|
||||
* that by remembering the lastOverflowedXid, ie the last thrown-away subXID.
|
||||
* As long as that is within the range of interesting XIDs, we have to assume
|
||||
* that subXIDs are missing from snapshots. (Note that subXID overflow occurs
|
||||
* on primary when 65th subXID arrives, whereas on standby it occurs when 64th
|
||||
|
@@ -99,7 +99,7 @@ InitRecoveryTransactionEnvironment(void)
|
||||
* Lock a virtual transaction id for Startup process.
|
||||
*
|
||||
* We need to do GetNextLocalTransactionId() because
|
||||
* SharedInvalBackendInit() leaves localTransactionid invalid and the lock
|
||||
* SharedInvalBackendInit() leaves localTransactionId invalid and the lock
|
||||
* manager doesn't like that at all.
|
||||
*
|
||||
* Note that we don't need to run XactLockTableInsert() because nobody
|
||||
|
@@ -232,7 +232,7 @@ LOG_LWDEBUG(const char *where, LWLock *lock, const char *msg)
|
||||
|
||||
static void init_lwlock_stats(void);
|
||||
static void print_lwlock_stats(int code, Datum arg);
|
||||
static lwlock_stats * get_lwlock_stats_entry(LWLock *lockid);
|
||||
static lwlock_stats * get_lwlock_stats_entry(LWLock *lock);
|
||||
|
||||
static void
|
||||
init_lwlock_stats(void)
|
||||
|
@@ -731,7 +731,7 @@ mdwrite(SMgrRelation reln, ForkNumber forknum, BlockNumber blocknum,
|
||||
* mdnblocks() -- Get the number of blocks stored in a relation.
|
||||
*
|
||||
* Important side effect: all active segments of the relation are opened
|
||||
* and added to the mdfd_seg_fds array. If this routine has not been
|
||||
* and added to the md_seg_fds array. If this routine has not been
|
||||
* called, then only segments up to the last one actually touched
|
||||
* are present in the array.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user