From: Heikki Linnakangas Date: Tue, 3 Sep 2013 10:17:09 +0000 (+0300) Subject: Fix typo in comment. X-Git-Tag: REL9_4_BETA1~1180 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a93bdfc711399716328ce0811d600411b1314306;p=postgresql Fix typo in comment. Also line-wrap an over-wide line in a comment that's ignored by pgindent. --- diff --git a/src/backend/replication/syncrep.c b/src/backend/replication/syncrep.c index 5424281b42..8cf1346c18 100644 --- a/src/backend/replication/syncrep.c +++ b/src/backend/replication/syncrep.c @@ -21,8 +21,9 @@ * * Replication is either synchronous or not synchronous (async). If it is * async, we just fastpath out of here. If it is sync, then we wait for - * the write or flush location on the standby before releasing the waiting backend. - * Further complexity in that interaction is expected in later releases. + * the write or flush location on the standby before releasing the waiting + * backend. Further complexity in that interaction is expected in later + * releases. * * The best performing way to manage the waiting backends is to have a * single ordered queue of waiting backends, so that we can avoid @@ -116,7 +117,7 @@ SyncRepWaitForLSN(XLogRecPtr XactCommitLSN) * set. See SyncRepUpdateSyncStandbysDefined. * * Also check that the standby hasn't already replied. Unlikely race - * condition but we'll be fetching that cache line anyway so its likely to + * condition but we'll be fetching that cache line anyway so it's likely to * be a low cost check. */ if (!WalSndCtl->sync_standbys_defined ||