Commit 35584fd0 authored by Peter Eisentraut's avatar Peter Eisentraut

Make spelling of "acknowledgment" consistent

I used the preferred U.S. spelling, as we do in other cases.
parent 9274c577
...@@ -1324,14 +1324,14 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' ...@@ -1324,14 +1324,14 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
</para> </para>
<para> <para>
If primary restarts while commits are waiting for acknowledgement, those If primary restarts while commits are waiting for acknowledgment, those
waiting transactions will be marked fully committed once the primary waiting transactions will be marked fully committed once the primary
database recovers. database recovers.
There is no way to be certain that all standbys have received all There is no way to be certain that all standbys have received all
outstanding WAL data at time of the crash of the primary. Some outstanding WAL data at time of the crash of the primary. Some
transactions may not show as committed on the standby, even though transactions may not show as committed on the standby, even though
they show as committed on the primary. The guarantee we offer is that they show as committed on the primary. The guarantee we offer is that
the application will not receive explicit acknowledgement of the the application will not receive explicit acknowledgment of the
successful commit of a transaction until the WAL data is known to be successful commit of a transaction until the WAL data is known to be
safely received by all the synchronous standbys. safely received by all the synchronous standbys.
</para> </para>
......
...@@ -5890,7 +5890,7 @@ This was disabled in the PG 9.6 branch so there is no commit here. ...@@ -5890,7 +5890,7 @@ This was disabled in the PG 9.6 branch so there is no commit here.
2016-12-19 [3901fd70c] Support quorum-based synchronous replication. 2016-12-19 [3901fd70c] Support quorum-based synchronous replication.
--> -->
<para> <para>
Allow waiting for commit acknowledgement from standby Allow waiting for commit acknowledgment from standby
servers irrespective of the order they appear in <xref servers irrespective of the order they appear in <xref
linkend="guc-synchronous-standby-names"/> (Masahiko Sawada) linkend="guc-synchronous-standby-names"/> (Masahiko Sawada)
</para> </para>
...@@ -6462,7 +6462,7 @@ This was disabled in the PG 9.6 branch so there is no commit here. ...@@ -6462,7 +6462,7 @@ This was disabled in the PG 9.6 branch so there is no commit here.
<para> <para>
This is useful for checking after an abrupt disconnection whether This is useful for checking after an abrupt disconnection whether
your previous transaction committed and you just didn't receive your previous transaction committed and you just didn't receive
the acknowledgement. the acknowledgment.
</para> </para>
</listitem> </listitem>
......
...@@ -268,7 +268,7 @@ SyncRepWaitForLSN(XLogRecPtr lsn, bool commit) ...@@ -268,7 +268,7 @@ SyncRepWaitForLSN(XLogRecPtr lsn, bool commit)
/* /*
* If the postmaster dies, we'll probably never get an * If the postmaster dies, we'll probably never get an
* acknowledgement, because all the wal sender processes will exit. So * acknowledgment, because all the wal sender processes will exit. So
* just bail out. * just bail out.
*/ */
if (!PostmasterIsAlive()) if (!PostmasterIsAlive())
......
...@@ -159,7 +159,7 @@ ...@@ -159,7 +159,7 @@
* scanned for the history add's, otherwise a literal character * scanned for the history add's, otherwise a literal character
* is omitted and only his history entry added. * is omitted and only his history entry added.
* *
* Acknowledgements: * Acknowledgments:
* *
* Many thanks to Adisak Pochanayon, who's article about SLZ * Many thanks to Adisak Pochanayon, who's article about SLZ
* inspired me to write the PostgreSQL compression this way. * inspired me to write the PostgreSQL compression this way.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment