|
1 | 1 | <!-- |
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 $ |
3 | 3 |
|
4 | 4 | Typical markup: |
5 | 5 |
|
@@ -376,6 +376,21 @@ pg_[A-Za-z0-9_] <application> |
376 | 376 | </para> |
377 | 377 | </listitem> |
378 | 378 |
|
| 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 | + |
379 | 394 | <listitem> |
380 | 395 | <para> |
381 | 396 | In <application>psql</application>, treat unquoted |
|