提交 5d9c6b18 编写于 作者: T Tom Lane

Document change in large object snapshotting behavior as a version

compatibility issue.
上级 8a65b820
<!--
$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
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册