aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2020-08-31 15:23:18 -0400
committerBruce Momjian <bruce@momjian.us>2020-08-31 15:23:18 -0400
commit851e0f07a1478b4aecddf881f0608ef4d60bec98 (patch)
tree67e068d6028b710f865e31da35abca69b70cd581
parent58eb1760baa67a36e71b26f9ed2ddc86a1cac03d (diff)
downloadpostgresql-851e0f07a1478b4aecddf881f0608ef4d60bec98.tar.gz
postgresql-851e0f07a1478b4aecddf881f0608ef4d60bec98.zip
docs: replace "stable storage" with "durable" in descriptions
For PG, "durable storage" has a clear meaning, while "stable storage" does not, so use the former. Discussion: https://postgr.es/m/20200817165222.GA31806@momjian.us Backpatch-through: 9.5
-rw-r--r--doc/src/sgml/config.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 74bb25ae16e..ad4f13277fc 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2122,7 +2122,7 @@ include_dir 'conf.d'
until a reply from the current synchronous standby indicates it has
received the commit record of the transaction and written it out to
the standby's operating system, but the data has not necessarily
- reached stable storage on the standby. This setting is sufficient to
+ reached durable storage on the standby. This setting is sufficient to
ensure data preservation even if the standby instance of
<productname>PostgreSQL</> were to crash, but not if the standby
suffers an operating-system-level crash.