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
d309acf2
Commit
d309acf2
authored
14 years ago
by
Robert Haas
Browse files
Options
Downloads
Patches
Plain Diff
Typo fixes. receivedUpto should be capitalized consistently.
parent
2c20ba1f
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
src/backend/replication/README
+2
-2
2 additions, 2 deletions
src/backend/replication/README
src/backend/replication/walreceiver.c
+1
-1
1 addition, 1 deletion
src/backend/replication/walreceiver.c
with
3 additions
and
3 deletions
src/backend/replication/README
+
2
−
2
View file @
d309acf2
...
...
@@ -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->receivedUp
T
o.
and initializes the starting point in WalRcvData->receivedUp
t
o.
As walreceiver receives WAL from the master server, and writes and flushes
it to disk (in pg_xlog), it updates WalRcvData->receivedUp
T
o. Startup process
it to disk (in pg_xlog), it updates WalRcvData->receivedUp
t
o. Startup process
polls that to know how far it can proceed with WAL replay.
Walsender IPC
...
...
This diff is collapsed.
Click to expand it.
src/backend/replication/walreceiver.c
+
1
−
1
View file @
d309acf2
...
...
@@ -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->receivedUp
T
o variable in shared memory, to inform the startup
* WalRcv->receivedUp
t
o 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
...
...
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