|
1 | 1 | <!--
|
2 |
| -$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.16 2002/04/23 02:07:15 tgl Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.17 2002/08/10 20:43:46 momjian Exp $ |
3 | 3 | PostgreSQL documentation
|
4 | 4 | -->
|
5 | 5 |
|
@@ -75,19 +75,6 @@ CLUSTER
|
75 | 75 | </varlistentry>
|
76 | 76 | <varlistentry>
|
77 | 77 | <term><computeroutput>
|
78 |
| -ERROR: relation <<replaceable class="PARAMETER">tablerelation_number</replaceable>> inherits "<replaceable class="PARAMETER">table</replaceable>" |
79 |
| - </computeroutput></term> |
80 |
| - <listitem> |
81 |
| - <para> |
82 |
| - <comment> |
83 |
| - This is not documented anywhere. It seems not to be possible to |
84 |
| - cluster a table that is inherited. |
85 |
| - </comment> |
86 |
| - </para> |
87 |
| - </listitem> |
88 |
| - </varlistentry> |
89 |
| - <varlistentry> |
90 |
| - <term><computeroutput> |
91 | 78 | ERROR: Relation <replaceable class="PARAMETER">table</replaceable> does not exist!
|
92 | 79 | </computeroutput></term>
|
93 | 80 | <listitem>
|
@@ -138,13 +125,6 @@ ERROR: Relation <replaceable class="PARAMETER">table</replaceable> does not exis
|
138 | 125 | Notes
|
139 | 126 | </title>
|
140 | 127 |
|
141 |
| - <para> |
142 |
| - The table is actually copied to a temporary table in index |
143 |
| - order, then renamed back to the original name. For this |
144 |
| - reason, all grant permissions and other indexes are lost |
145 |
| - when clustering is performed. |
146 |
| - </para> |
147 |
| - |
148 | 128 | <para>
|
149 | 129 | In cases where you are accessing single rows randomly
|
150 | 130 | within a table, the actual order of the data in the heap
|
@@ -194,6 +174,20 @@ SELECT <replaceable class="parameter">columnlist</replaceable> INTO TABLE <repla
|
194 | 174 | fast because most of the heap data has already been
|
195 | 175 | ordered, and the existing index is used.
|
196 | 176 | </para>
|
| 177 | + |
| 178 | + <para> |
| 179 | + During the cluster operation, a temporal table is created that contains |
| 180 | + the table in the index order. Due to this, you need to have free space |
| 181 | + on disk at least the size of the table itself, or the biggest index if |
| 182 | + you have one that is larger than the table. |
| 183 | + </para> |
| 184 | + |
| 185 | + <para> |
| 186 | + As opposed to previous releases, CLUSTER does not lose GRANT, |
| 187 | + inheritance or foreign key information, and preserves indexes |
| 188 | + other than the one being used for the CLUSTER. |
| 189 | + </para> |
| 190 | + |
197 | 191 | </refsect2>
|
198 | 192 | </refsect1>
|
199 | 193 |
|
|
0 commit comments