database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-02 11:44:50 +03:00
Code

Fix function names in comments.

Browse Source 
Commit 3eb77eba5a renamed some functions, but forgot to
update some comments referencing to those functions.
This commit fixes those function names in the comments.

Kyotaro Horiguchi
This commit is contained in:
Fujii Masao 2019-04-25 23:43:48 +09:00
parent 87259588d0
commit 978b032d1f
4 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/backend/postmaster/checkpointer.c
View File

@ -137,7 +137,7 @@ typedef struct
static CheckpointerShmemStruct *CheckpointerShmem; static CheckpointerShmemStruct *CheckpointerShmem;
/* interval for calling AbsorbFsyncRequests in CheckpointWriteDelay */ /* interval for calling AbsorbSyncRequests in CheckpointWriteDelay */
#define WRITES_PER_ABSORB 1000 #define WRITES_PER_ABSORB 1000
/* /*

2
src/backend/storage/smgr/md.c
View File

@ -952,7 +952,7 @@ register_forget_request(RelFileNodeBackend rnode, ForkNumber forknum,
} }
/* /*
* ForgetDatabaseFsyncRequests -- forget any fsyncs and unlinks for a DB * ForgetDatabaseSyncRequests -- forget any fsyncs and unlinks for a DB
*/ */
void void
ForgetDatabaseSyncRequests(Oid dbid) ForgetDatabaseSyncRequests(Oid dbid)

8
src/backend/storage/sync/sync.c
View File

@ -75,7 +75,7 @@ static MemoryContext pendingOpsCxt; /* context for the above */
static CycleCtr sync_cycle_ctr = 0; static CycleCtr sync_cycle_ctr = 0;
static CycleCtr checkpoint_cycle_ctr = 0; static CycleCtr checkpoint_cycle_ctr = 0;
/* Intervals for calling AbsorbFsyncRequests */ /* Intervals for calling AbsorbSyncRequests */
#define FSYNCS_PER_ABSORB 10 #define FSYNCS_PER_ABSORB 10
#define UNLINKS_PER_ABSORB 10 #define UNLINKS_PER_ABSORB 10
@ -215,9 +215,9 @@ SyncPostCheckpoint(void)
pfree(entry); pfree(entry);
/* /*
* As in ProcessFsyncRequests, we don't want to stop absorbing fsync * As in ProcessSyncRequests, we don't want to stop absorbing fsync
* requests for along time when there are many deletions to be done. * requests for along time when there are many deletions to be done.
* We can safely call AbsorbFsyncRequests() at this point in the loop * We can safely call AbsorbSyncRequests() at this point in the loop
* (note it might try to delete list entries). * (note it might try to delete list entries).
*/ */
if (--absorb_counter <= 0) if (--absorb_counter <= 0)
@ -284,7 +284,7 @@ ProcessSyncRequests(void)
* eventually wrap the counter around to the point where an old entry * eventually wrap the counter around to the point where an old entry
* might appear new, causing us to skip it, possibly allowing a checkpoint * might appear new, causing us to skip it, possibly allowing a checkpoint
* to succeed that should not have. To forestall wraparound, any time the * to succeed that should not have. To forestall wraparound, any time the
* previous ProcessFsyncRequests() failed to complete, run through the * previous ProcessSyncRequests() failed to complete, run through the
* table and forcibly set cycle_ctr = sync_cycle_ctr. * table and forcibly set cycle_ctr = sync_cycle_ctr.
* *
* Think not to merge this loop with the main loop, as the problem is * Think not to merge this loop with the main loop, as the problem is

2
src/common/rmtree.c
View File

@ -68,7 +68,7 @@ rmtree(const char *path, bool rmtopdir)
* This is not an academic possibility. One scenario where this * This is not an academic possibility. One scenario where this
* happens is when bgwriter has a pending unlink request for a file in * happens is when bgwriter has a pending unlink request for a file in
* a database that's being dropped. In dropdb(), we call * a database that's being dropped. In dropdb(), we call
* ForgetDatabaseFsyncRequests() to flush out any such pending unlink * ForgetDatabaseSyncRequests() to flush out any such pending unlink
* requests, but because that's asynchronous, it's not guaranteed that * requests, but because that's asynchronous, it's not guaranteed that
* the bgwriter receives the message in time. * the bgwriter receives the message in time.
*/ */