|
21 | 21 | *
|
22 | 22 | * Replication is either synchronous or not synchronous (async). If it is
|
23 | 23 | * async, we just fastpath out of here. If it is sync, then we wait for
|
24 |
| - * the write or flush location on the standby before releasing the waiting backend. |
25 |
| - * Further complexity in that interaction is expected in later releases. |
| 24 | + * the write or flush location on the standby before releasing the waiting |
| 25 | + * backend. Further complexity in that interaction is expected in later |
| 26 | + * releases. |
26 | 27 | *
|
27 | 28 | * The best performing way to manage the waiting backends is to have a
|
28 | 29 | * single ordered queue of waiting backends, so that we can avoid
|
@@ -116,7 +117,7 @@ SyncRepWaitForLSN(XLogRecPtr XactCommitLSN)
|
116 | 117 | * set. See SyncRepUpdateSyncStandbysDefined.
|
117 | 118 | *
|
118 | 119 | * Also check that the standby hasn't already replied. Unlikely race
|
119 |
| - * condition but we'll be fetching that cache line anyway soits likely to |
| 120 | + * condition but we'll be fetching that cache line anyway soit's likely to |
120 | 121 | * be a low cost check.
|
121 | 122 | */
|
122 | 123 | if (!WalSndCtl->sync_standbys_defined||
|
|