diff options
| author | Robert Haas <rhaas@postgresql.org> | 2011-02-11 11:55:12 -0500 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2011-02-11 11:55:12 -0500 |
| commit | d309acf201ab2c5bbd1f6a5d51e4a8060eb6a63c (patch) | |
| tree | 72abe15d18423f94a49c41f35337214582ed5b1f | |
| parent | 2c20ba1fd284423e4652f2f6855d257339245e97 (diff) | |
| download | postgresql-d309acf201ab2c5bbd1f6a5d51e4a8060eb6a63c.tar.gz postgresql-d309acf201ab2c5bbd1f6a5d51e4a8060eb6a63c.zip | |
Typo fixes. receivedUpto should be capitalized consistently.
| -rw-r--r-- | src/backend/replication/README | 4 | ||||
| -rw-r--r-- | src/backend/replication/walreceiver.c | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/replication/README b/src/backend/replication/README index 9c2e0d8e974..744ddc7fe8f 100644 --- a/src/backend/replication/README +++ b/src/backend/replication/README @@ -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 diff --git a/src/backend/replication/walreceiver.c b/src/backend/replication/walreceiver.c index 30e35dbd28a..3277da8fc33 100644 --- a/src/backend/replication/walreceiver.c +++ b/src/backend/replication/walreceiver.c @@ -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 |