database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

Document change in large object snapshotting behavior as a version

Browse Source 
compatibility issue.
This commit is contained in:
Tom Lane 2005-09-24 20:35:21 +00:00
parent 8a65b820e2
commit 5d9c6b18d3
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/src/sgml/release.sgml
View File

@ -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