Skip to content
Snippets Groups Projects
Commit d309acf2 authored by Robert Haas's avatar Robert Haas
Browse files

Typo fixes. receivedUpto should be capitalized consistently.

parent 2c20ba1f
No related branches found
No related tags found
No related merge requests found
......@@ -45,10 +45,10 @@ to fetch more WAL (if streaming replication is configured).
Walreceiver is a postmaster subprocess, so the startup process can't fork it
directly. Instead, it sends a signal to postmaster, asking postmaster to launch
it. Before that, however, startup process fills in WalRcvData->conninfo,
and initializes the starting point in WalRcvData->receivedUpTo.
and initializes the starting point in WalRcvData->receivedUpto.
As walreceiver receives WAL from the master server, and writes and flushes
it to disk (in pg_xlog), it updates WalRcvData->receivedUpTo. Startup process
it to disk (in pg_xlog), it updates WalRcvData->receivedUpto. Startup process
polls that to know how far it can proceed with WAL replay.
Walsender IPC
......
......@@ -12,7 +12,7 @@
* in the primary server), and then keeps receiving XLOG records and
* writing them to the disk as long as the connection is alive. As XLOG
* records are received and flushed to disk, it updates the
* WalRcv->receivedUpTo variable in shared memory, to inform the startup
* WalRcv->receivedUpto variable in shared memory, to inform the startup
* process of how far it can proceed with XLOG replay.
*
* Normal termination is by SIGTERM, which instructs the walreceiver to
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment