If PostgreSQL failed to compile on your computer or you found a bug that is likely to be specific to one platform then please fill out this form and e-mail it to pgsql-ports@postgresql.org. To report any other bug, fill out the form below and e-mail it to pgsql-bugs@postgresql.org. If you not only found the problem but solved it and generated a patch then e-mail it to pgsql-patches@postgresql.org instead. Please use the command "diff -c" to generate the patch. You may also enter a bug report at http://www.postgresql.org/ instead of e-mail-ing this form. ============================================================================ POSTGRESQL BUG REPORT TEMPLATE ============================================================================ Your name : Darren Steven Your email address : dsteven@nettas.telstra.com.au System Configuration --------------------- Architecture (example: Intel Pentium) : Intel PIII Operating System (example: Linux 2.0.26 ELF) : Linux 2.2.14 PostgreSQL version (example: PostgreSQL-6.5.1): PostgreSQL-7.0 Compiler used (example: gcc 2.8.0) : egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Please enter a FULL description of your problem: ------------------------------------------------ CLUSTER fails and appears to corrupt database. I don't know if this happened on other releases, found it by mistake while playing with 7.0 PS Great DB by the way. Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: ---------------------------------------------------------------------- Create a database, create a table. insert some data. create index on one of fields. CLUSTER indexname ON tablename; With a large number of rows (so I can see it happeneing), I see the table being copied to a temp, and the renamed back to its original name. the problem is with the index : dws=# create index testind on accesslog (alclient); CREATE dws=# cluster testind on accesslog; ERROR: temp_674e00 is an index relation temp_674e00 appears to be a copy of the index file. psql now tells me the relation accesslog no longer exists the same error also occurs on small tables. If you know how this problem might be fixed, list the solution below: --------------------------------------------------------------------- Sorry. I've looked at cluster.c and if I fix it I'll post it.