diff options
| author | Robert Haas | 2012-08-21 15:08:15 +0000 |
|---|---|---|
| committer | Robert Haas | 2012-08-21 15:10:17 +0000 |
| commit | 82ef3d3008f8ec9c565f7a5724196cd0f342d594 (patch) | |
| tree | 191f159dbf61884a11bef2cd7316ee205fe1634c | |
| parent | 71450d7fd6c7cf7b3e38ac56e363bff6a681973c (diff) | |
Add a note to the MVCC chapter that some things aren't transactional.
Craig Ringer, slightly edited by me.
| -rw-r--r-- | doc/src/sgml/mvcc.sgml | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index 8f8858294dc..d5c6076d4aa 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -260,6 +260,18 @@ command <xref linkend="sql-set-transaction">. </para> + <important> + <para> + Some <productname>PostgreSQL</productname> data types and functions have + special rules regarding transactional behaviour. In particular, changes + made to a <literal>SEQUENCE</literal> (and therefore the counter of a + column declared using <literal>SERIAL</literal>) are immediately visible + to all other transactions and are not rolled back if the transaction + that made the changes aborts. See <xref linkend="functions-sequence"> + and <xref linkend="datatype-serial">. + </para> + </important> + <sect2 id="xact-read-committed"> <title>Read Committed Isolation Level</title> |