|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.13 2001/12/08 03:24:34 thomas Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.14 2001/12/30 04:36:52 tgl Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -190,8 +190,8 @@ SELECT <replaceable class="parameter">columnlist</replaceable> INTO TABLE <repla |
190 | 190 | the ORDER BY clause to match the index, and which is much faster for |
191 | 191 | unordered data. You then drop the old table, use |
192 | 192 | <command>ALTER TABLE...RENAME</command> |
193 | | - to rename <replaceable class="parameter">temp</replaceable> to the old name, and |
194 | | - recreate any indexes. The only problem is that <acronym>OID</acronym>s |
| 193 | + to rename <replaceable class="parameter">newtable</replaceable> to the old name, and |
| 194 | + recreate the table's indexes. The only problem is that <acronym>OID</acronym>s |
195 | 195 | will not be preserved. From then on, <command>CLUSTER</command> should be |
196 | 196 | fast because most of the heap data has already been |
197 | 197 | ordered, and the existing index is used. |
|