database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-18 17:41:14 +03:00
Code

Document that CLUSTER breaks MVCC visibility rules.

Browse Source 
(Not needed in cvs head, because CLUSTER itself is fixed there)

Heikki Linnakangas
This commit is contained in:
Magnus Hagander 2007-05-13 16:04:22 +00:00
parent e449e19124
commit 7ee0498772
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/sgml/ref/cluster.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.30 2003/11/02 12:59:54 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.30.2.1 2007/05/13 16:04:22 mha Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -99,6 +99,17 @@ CLUSTER
<refsect1> <refsect1>
<title>Notes</title> <title>Notes</title>
<para>
<command>CLUSTER</command> loses all visibility information of tuples,
which makes the table look empty to any snapshot that was taken
before the <command>CLUSTER</command> command finished. That makes
<command>CLUSTER</command> unsuitable for applications where
transactions that access the table being clustered are run concurrently
with <command>CLUSTER</command>. This is most visible with serializable
transactions, because they take only one snapshot at the beginning of the
transaction, but read-committed transactions are also affected.
</para>
<para> <para>
In cases where you are accessing single rows randomly In cases where you are accessing single rows randomly
within a table, the actual order of the data in the within a table, the actual order of the data in the