postgres.git / summary / log / commit / refs

commit    8e0bcdc855c4976a31f9fd03e80b2c996f30fd27
Author:   Magnus Hagander <magnus@hagander.net>
Date:     Sun May 13 16:04:28 2007 +0000
First released in: 7.4.18, 8.0.14, 8.1.10, 8.2.5

    Document that CLUSTER breaks MVCC visibility rules.
    (Not needed in cvs head, because CLUSTER itself is fixed there)
    
    Heikki Linnakangas


 doc/src/sgml/ref/cluster.sgml | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml
index 19e8064b172..e1ac13fd589 100644
--- a/doc/src/sgml/ref/cluster.sgml
+++ b/doc/src/sgml/ref/cluster.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/cluster.sgml,v 1.35 2005/01/04 00:39:53 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/cluster.sgml,v 1.35.4.1 2007/05/13 16:04:28 mha Exp $
 PostgreSQL documentation
 -->
 
@@ -99,6 +99,17 @@ CLUSTER
  <refsect1>
   <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>
     In cases where you are accessing single rows randomly
     within a table, the actual order of the data in the


[parent: 3afb834ab6eb]