File tree Expand file tree Collapse file tree 2 files changed +3
-3
lines changed Expand file tree Collapse file tree 2 files changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -45,10 +45,10 @@ to fetch more WAL (if streaming replication is configured).
45
45
Walreceiver is a postmaster subprocess, so the startup process can't fork it
46
46
directly. Instead, it sends a signal to postmaster, asking postmaster to launch
47
47
it. Before that, however, startup process fills in WalRcvData->conninfo,
48
- and initializes the starting point in WalRcvData->receivedUpTo .
48
+ and initializes the starting point in WalRcvData->receivedUpto .
49
49
50
50
As walreceiver receives WAL from the master server, and writes and flushes
51
- it to disk (in pg_xlog), it updates WalRcvData->receivedUpTo . Startup process
51
+ it to disk (in pg_xlog), it updates WalRcvData->receivedUpto . Startup process
52
52
polls that to know how far it can proceed with WAL replay.
53
53
54
54
Walsender IPC
Original file line number Diff line number Diff line change 12
12
* in the primary server), and then keeps receiving XLOG records and
13
13
* writing them to the disk as long as the connection is alive. As XLOG
14
14
* records are received and flushed to disk, it updates the
15
- * WalRcv->receivedUpTo variable in shared memory, to inform the startup
15
+ * WalRcv->receivedUpto variable in shared memory, to inform the startup
16
16
* process of how far it can proceed with XLOG replay.
17
17
*
18
18
* Normal termination is by SIGTERM, which instructs the walreceiver to
You can’t perform that action at this time.
0 commit comments