mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Minor typos / copy-editing for snapmgr.c

Browse Source 
Noticed while reviewing snapshot management.
This commit is contained in:
Stephen Frost 2016-06-07 11:14:48 -04:00
parent d8c2dccfdb
commit 40fc457520
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/backend/utils/time/snapmgr.c
View File

@ -20,7 +20,7 @@
* tracked by any resource owner. * tracked by any resource owner.
* *
* The same is true for historic snapshots used during logical decoding, * The same is true for historic snapshots used during logical decoding,
* their lifetime is managed separately (as they life longer as one xact.c * their lifetime is managed separately (as they live longer as one xact.c
* transaction). * transaction).
* *
* These arrangements let us reset MyPgXact->xmin when there are no snapshots * 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. * Snapshot fields to be serialized.
* *
* Only these fields need to be sent to the cooperating backend; the * 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 typedef struct SerializedSnapshotData
{ {
@ -709,8 +709,8 @@ UpdateActiveSnapshotCommandId(void)
/* /*
* Don't allow modification of the active snapshot during parallel * Don't allow modification of the active snapshot during parallel
* operation. We share the snapshot to worker backends at beginning of * operation. We share the snapshot to worker backends at the beginning of
* parallel operation, so any change to snapshot can lead to * parallel operation, so any change to the snapshot can lead to
* inconsistencies. We have other defenses against * inconsistencies. We have other defenses against
* CommandCounterIncrement, but there are a few places that call this * CommandCounterIncrement, but there are a few places that call this
* directly, so we put an additional guard here. * directly, so we put an additional guard here.
@ -1892,7 +1892,7 @@ HistoricSnapshotGetTupleCids(void)
/* /*
* EstimateSnapshotSpace * EstimateSnapshotSpace
* Returns the size need to store the given snapshot. * Returns the size needed to store the given snapshot.
* *
* We are exporting only required fields from the Snapshot, stored in * We are exporting only required fields from the Snapshot, stored in
* SerializedSnapshotData. * SerializedSnapshotData.