Skip to content

Commit 5d9c6b1

Browse files
committed
Document change in large object snapshotting behavior as a version
compatibility issue.
1 parent 8a65b82 commit 5d9c6b1

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

doc/src/sgml/release.sgml

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.374 2005/09/23 16:36:35 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.375 2005/09/24 20:35:21 tgl Exp $
33

44
Typical markup:
55

@@ -376,6 +376,21 @@ pg_[A-Za-z0-9_] <application>
376376
</para>
377377
</listitem>
378378

379+
<listitem>
380+
<para>
381+
Read-only large object descriptors now obey MVCC snapshot semantics
382+
</para>
383+
<para>
384+
When a large object is opened with <literal>INV_READ</> (and not
385+
<literal>INV_WRITE</>), the data read from the descriptor will now
386+
reflect a <quote>snapshot</> of the large object's state at the
387+
time of the transaction snapshot in use by the query that called
388+
<function>lo_open()</>. To obtain the old behavior of always
389+
returning the latest committed data, include <literal>INV_WRITE</>
390+
in the mode flags for <function>lo_open()</>.
391+
</para>
392+
</listitem>
393+
379394
<listitem>
380395
<para>
381396
In <application>psql</application>, treat unquoted

0 commit comments

Comments
 (0)