Document change in large object snapshotting behavior as a version

compatibility issue.

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 0456bb4631a140729928e30a34156a6c8e01d183..4e5344b519d5289b898cc5148c4f7bc420d205d8 100644 (file)
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -376,6 +376,21 @@ pg_[A-Za-z0-9_]                 <application>
       </para>
      </listitem>
 
+     <listitem>
+      <para>
+       Read-only large object descriptors now obey MVCC snapshot semantics
+      </para>
+      <para>
+       When a large object is opened with <literal>INV_READ</> (and not
+       <literal>INV_WRITE</>), the data read from the descriptor will now
+       reflect a <quote>snapshot</> of the large object's state at the
+       time of the transaction snapshot in use by the query that called
+       <function>lo_open()</>.  To obtain the old behavior of always
+       returning the latest committed data, include <literal>INV_WRITE</>
+       in the mode flags for <function>lo_open()</>.
+      </para>
+     </listitem>
+
      <listitem>
       <para>
        In <application>psql</application>, treat unquoted