summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-05-05 14:57:16 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-05-05 14:57:16 -0400
commit69fc9430b892c737efa86e70fde7b4fd43974b10 (patch)
treea701b20c38246e41e8a5cf778980f73c8910bd9c
parent000f557c3111add0e5aa28936ba8ad49ff896667 (diff)
Release notes for 11.3, 10.8, 9.6.13, 9.5.17, 9.4.22.
-rw-r--r--doc/src/sgml/release-11.sgml11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/src/sgml/release-11.sgml b/doc/src/sgml/release-11.sgml
index 3156cc7c108..373b8de09ac 100644
--- a/doc/src/sgml/release-11.sgml
+++ b/doc/src/sgml/release-11.sgml
@@ -514,14 +514,15 @@ Branch: REL9_4_STABLE [ede6b1962] 2019-02-25 00:02:56 +1300
-->
<para>
Tolerate <literal>EINVAL</literal> and <literal>ENOSYS</literal>
- error results, where appropriate, for fsync calls (Thomas Munro,
- James Sewell)
+ error results, where appropriate, for <function>fsync</function>
+ and <function>sync_file_range</function> calls
+ (Thomas Munro, James Sewell)
</para>
<para>
- The previous change to panic on fsync failures turns out to have
- been excessively paranoid for certain cases where a failure is
- predictable and essentially means <quote>operation not
+ The previous change to panic on file synchronization failures turns
+ out to have been excessively paranoid for certain cases where a
+ failure is predictable and essentially means <quote>operation not
supported</quote>.
</para>
</listitem>