Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
40fc4575
Commit
40fc4575
authored
Jun 07, 2016
by
Stephen Frost
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor typos / copy-editing for snapmgr.c
Noticed while reviewing snapshot management.
parent
d8c2dccf
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
src/backend/utils/time/snapmgr.c
src/backend/utils/time/snapmgr.c
+5
-5
No files found.
src/backend/utils/time/snapmgr.c
View file @
40fc4575
...
...
@@ -20,7 +20,7 @@
* tracked by any resource owner.
*
* The same is true for historic snapshots used during logical decoding,
* their lifetime is managed separately (as they li
f
e longer as one xact.c
* their lifetime is managed separately (as they li
v
e longer as one xact.c
* transaction).
*
* These arrangements let us reset MyPgXact->xmin when there are no snapshots
...
...
@@ -228,7 +228,7 @@ static void SnapshotResetXmin(void);
* Snapshot fields to be serialized.
*
* Only these fields need to be sent to the cooperating backend; the
* remaining ones can (and must) set by the receiver upon restore.
* remaining ones can (and must)
be
set by the receiver upon restore.
*/
typedef
struct
SerializedSnapshotData
{
...
...
@@ -709,8 +709,8 @@ UpdateActiveSnapshotCommandId(void)
/*
* Don't allow modification of the active snapshot during parallel
* operation. We share the snapshot to worker backends at beginning of
* parallel operation, so any change to snapshot can lead to
* operation. We share the snapshot to worker backends at
the
beginning of
* parallel operation, so any change to
the
snapshot can lead to
* inconsistencies. We have other defenses against
* CommandCounterIncrement, but there are a few places that call this
* directly, so we put an additional guard here.
...
...
@@ -1892,7 +1892,7 @@ HistoricSnapshotGetTupleCids(void)
/*
* EstimateSnapshotSpace
* Returns the size need to store the given snapshot.
* Returns the size need
ed
to store the given snapshot.
*
* We are exporting only required fields from the Snapshot, stored in
* SerializedSnapshotData.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment