Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E2DC32E32D7 for ; Fri, 8 Feb 2008 12:35:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 09270-01 for ; Fri, 8 Feb 2008 12:35:32 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D904C2E319B for ; Fri, 8 Feb 2008 12:35:32 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m18GZU7f002026; Fri, 8 Feb 2008 11:35:30 -0500 (EST) To: "Mark Steben" cc: pgsql-admin@postgresql.org Subject: Re: Error on CLUSTER command In-reply-to: <00b101c86a6f$3eef3f80$14010a0a@dei26g028575> References: <00b101c86a6f$3eef3f80$14010a0a@dei26g028575> Comments: In-reply-to "Mark Steben" message dated "Fri, 08 Feb 2008 11:25:40 -0500" Date: Fri, 08 Feb 2008 11:35:30 -0500 Message-ID: <2025.1202488530@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/103 X-Sequence-Number: 28177 "Mark Steben" writes: > The number may change pointing to another index or stay the same. > The error persists if I repeat 3 or 4 times. Usually after the > 4th or 5th time the cluster is successful. Hm. I'd guess that the installation is old enough that the OID counter has wrapped around, and is currently in a region that is pretty densely populated with existing tables. (You could check that out by looking into the database directory.) 7.4.x doesn't have the logic that was added later to skip over filenames that are already in use; instead you just get an error if there's a collision. I forget whether 7.4's pg_resetxlog has an option to set the OID counter, but if it does then a temporary fix is to move the OID counter to some less densely populated range. > What is the risk of performing an upgrade to 7.4.19? Low, but it won't make this particular problem go away. regards, tom lane