Index: doc/src/sgml/ref/cluster.sgml =================================================================== RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v retrieving revision 1.16 diff -c -r1.16 cluster.sgml *** doc/src/sgml/ref/cluster.sgml 2002/04/23 02:07:15 1.16 --- doc/src/sgml/ref/cluster.sgml 2002/07/14 21:25:24 *************** *** 75,93 **** - ERROR: relation <tablerelation_number> inherits "table" - - - - - This is not documented anywhere. It seems not to be possible to - cluster a table that is inherited. - - - - - - ERROR: Relation table does not exist! --- 75,80 ---- *************** *** 139,151 **** - The table is actually copied to a temporary table in index - order, then renamed back to the original name. For this - reason, all grant permissions and other indexes are lost - when clustering is performed. - - - In cases where you are accessing single rows randomly within a table, the actual order of the data in the heap table is unimportant. However, if you tend to access some --- 126,131 ---- *************** *** 194,199 **** --- 174,192 ---- fast because most of the heap data has already been ordered, and the existing index is used. + + + During the cluster operation, a temporal table is created that + contains the table in the index order. Due to this, you need + to have free space on disk at least the size of the table itself. + + + + As opposed to previous releases, CLUSTER does not lose GRANT, + inheritance or foreign key information, and preserves indexes + other than the one being used for the CLUSTER. + +