database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-10 17:42:29 +03:00
Code Activity

Standardize "WAL location" terminology

Browse Source 
Other previously used terms were "WAL position" or "log position".
This commit is contained in:
Peter Eisentraut
2017-05-12 13:51:27 -04:00
parent c1a7f64b4a
commit d496a65790
19 changed files with 62 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/backend/replication/walreceiver.c
View File

@@ -1090,7 +1090,7 @@ XLogWalRcvFlush(bool dying)
}
/*
* Send reply message to primary, indicating our current XLOG positions, oldest
* Send reply message to primary, indicating our current WAL locations, oldest
* xmin and the current time.
*
* If 'force' is not set, the message is only sent if enough time has
@@ -1125,7 +1125,7 @@ XLogWalRcvSendReply(bool force, bool requestReply)
* We can compare the write and flush positions to the last message we
* sent without taking any lock, but the apply position requires a spin
* lock, so we don't check that unless something else has changed or 10
* seconds have passed. This means that the apply log position will
* seconds have passed. This means that the apply WAL location will
* appear, from the master's point of view, to lag slightly, but since
* this is only for reporting purposes and only on idle systems, that's
* probably OK.