From 5d9c6b18d30daa35e59c89f33c685e0133da0bf4 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sat, 24 Sep 2005 20:35:21 +0000
Subject: [PATCH] Document change in large object snapshotting behavior as a
version compatibility issue.
---
doc/src/sgml/release.sgml | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index c79bbc8048e..7660d338f40 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.374 2005/09/23 16:36:35 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.375 2005/09/24 20:35:21 tgl Exp $
Typical markup:
@@ -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
--
GitLab