Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit fe811ae

Browse files
committed
Fix typos in README.
1 parent e5db11c commit fe811ae

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/backend/replication/README

+3-3
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Disconnect.
3636

3737
This API should be considered internal at the moment, but we could open it
3838
up for 3rd party replacements of libpqwalreceiver in the future, allowing
39-
pluggable methods for receiveing WAL.
39+
pluggable methods for receiving WAL.
4040

4141
Walreceiver IPC
4242
---------------
@@ -55,7 +55,7 @@ it to disk (in pg_xlog), it updates WalRcvData->receivedUpto and signals
5555
the startup process to know how far WAL replay can advance.
5656

5757
Walreceiver sends information about replication progress to the master server
58-
whenever either it writes or flushes new WAL, or the specified interval elapses.
58+
whenever it either writes or flushes new WAL, or the specified interval elapses.
5959
This is used for reporting purpose.
6060

6161
Walsender IPC
@@ -83,7 +83,7 @@ backends.
8383

8484
Note that no big harm is done if postmaster thinks that a walsender is a
8585
regular backend; it will just terminate the walsender earlier in the shutdown
86-
phase. A walsenders will look like a regular backends until it's done with the
86+
phase. A walsender will look like a regular backend until it's done with the
8787
initialization and has marked itself in PMSignal array, and at process
8888
termination, after unmarking the PMSignal slot.
8989

0 commit comments

Comments
 (0)