Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
35584fd0
Commit
35584fd0
authored
Oct 15, 2018
by
Peter Eisentraut
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Make spelling of "acknowledgment" consistent
I used the preferred U.S. spelling, as we do in other cases.
parent
9274c577
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
6 additions
and
6 deletions
+6
-6
doc/src/sgml/high-availability.sgml
doc/src/sgml/high-availability.sgml
+2
-2
doc/src/sgml/release-10.sgml
doc/src/sgml/release-10.sgml
+2
-2
src/backend/replication/syncrep.c
src/backend/replication/syncrep.c
+1
-1
src/common/pg_lzcompress.c
src/common/pg_lzcompress.c
+1
-1
No files found.
doc/src/sgml/high-availability.sgml
View file @
35584fd0
...
@@ -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 acknowledg
e
ment, 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 acknowledg
e
ment 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>
...
...
doc/src/sgml/release-10.sgml
View file @
35584fd0
...
@@ -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 acknowledg
e
ment 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 acknowledg
e
ment.
the acknowledgment.
</para>
</para>
</listitem>
</listitem>
...
...
src/backend/replication/syncrep.c
View file @
35584fd0
...
@@ -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
* acknowledg
e
ment, 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
())
...
...
src/common/pg_lzcompress.c
View file @
35584fd0
...
@@ -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.
*
*
* Acknowledg
e
ments:
* 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.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment