|
20 | 20 | * tracked by any resource owner. |
21 | 21 | * |
22 | 22 | * The same is true for historic snapshots used during logical decoding, |
23 | | - * their lifetime is managed separately (as theylife longer as one xact.c |
| 23 | + * their lifetime is managed separately (as theylive longer as one xact.c |
24 | 24 | * transaction). |
25 | 25 | * |
26 | 26 | * These arrangements let us reset MyPgXact->xmin when there are no snapshots |
@@ -228,7 +228,7 @@ static void SnapshotResetXmin(void); |
228 | 228 | * Snapshot fields to be serialized. |
229 | 229 | * |
230 | 230 | * Only these fields need to be sent to the cooperating backend; the |
231 | | - * remaining ones can (and must) set by the receiver upon restore. |
| 231 | + * remaining ones can (and must)beset by the receiver upon restore. |
232 | 232 | */ |
233 | 233 | typedefstructSerializedSnapshotData |
234 | 234 | { |
@@ -709,8 +709,8 @@ UpdateActiveSnapshotCommandId(void) |
709 | 709 |
|
710 | 710 | /* |
711 | 711 | * Don't allow modification of the active snapshot during parallel |
712 | | - * operation. We share the snapshot to worker backends at beginning of |
713 | | - * parallel operation, so any change to snapshot can lead to |
| 712 | + * operation. We share the snapshot to worker backends atthebeginning of |
| 713 | + * parallel operation, so any change tothesnapshot can lead to |
714 | 714 | * inconsistencies. We have other defenses against |
715 | 715 | * CommandCounterIncrement, but there are a few places that call this |
716 | 716 | * directly, so we put an additional guard here. |
@@ -1892,7 +1892,7 @@ HistoricSnapshotGetTupleCids(void) |
1892 | 1892 |
|
1893 | 1893 | /* |
1894 | 1894 | * EstimateSnapshotSpace |
1895 | | - *Returns the sizeneed to store the given snapshot. |
| 1895 | + *Returns the sizeneeded to store the given snapshot. |
1896 | 1896 | * |
1897 | 1897 | * We are exporting only required fields from the Snapshot, stored in |
1898 | 1898 | * SerializedSnapshotData. |
|