Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
fe811ae8
Commit
fe811ae8
authored
12 years ago
by
Heikki Linnakangas
Browse files
Options
Downloads
Patches
Plain Diff
Fix typos in README.
parent
e5db11c5
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/backend/replication/README
+3
-3
3 additions, 3 deletions
src/backend/replication/README
with
3 additions
and
3 deletions
src/backend/replication/README
+
3
−
3
View file @
fe811ae8
...
...
@@ -36,7 +36,7 @@ Disconnect.
This API should be considered internal at the moment, but we could open it
up for 3rd party replacements of libpqwalreceiver in the future, allowing
pluggable methods for receiv
e
ing WAL.
pluggable methods for receiving WAL.
Walreceiver IPC
---------------
...
...
@@ -55,7 +55,7 @@ it to disk (in pg_xlog), it updates WalRcvData->receivedUpto and signals
the startup process to know how far WAL replay can advance.
Walreceiver sends information about replication progress to the master server
whenever either
it
writes or flushes new WAL, or the specified interval elapses.
whenever
it
either writes or flushes new WAL, or the specified interval elapses.
This is used for reporting purpose.
Walsender IPC
...
...
@@ -83,7 +83,7 @@ backends.
Note that no big harm is done if postmaster thinks that a walsender is a
regular backend; it will just terminate the walsender earlier in the shutdown
phase. A walsender
s
will look like a regular backend
s
until it's done with the
phase. A walsender will look like a regular backend until it's done with the
initialization and has marked itself in PMSignal array, and at process
termination, after unmarking the PMSignal slot.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment