Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id AC8E72E3FE3 for ; Fri, 8 Feb 2008 15:37:28 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 69500-04 for ; Fri, 8 Feb 2008 15:37:24 -0400 (AST) Received: from mail.autorevenue.com (ip-208.178.167.106.gblx.net [208.178.167.106]) by postgresql.org (Postfix) with ESMTP id 3EB5D2E3FE0 for ; Fri, 8 Feb 2008 15:37:24 -0400 (AST) Received: (qmail 17288 invoked from network); 8 Feb 2008 14:38:04 -0500 Received: from unknown (HELO dei26g028575) (msteben@10.10.1.20) by mail.autorevenue.com with SMTP; 8 Feb 2008 14:38:04 -0500 From: "Mark Steben" To: "'Tom Lane'" Cc: Subject: Re: Error on CLUSTER command Date: Fri, 8 Feb 2008 14:37:02 -0500 Message-ID: <00bf01c86a89$fa4af7a0$14010a0a@dei26g028575> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992 thread-index: AchqcMOQQQFck8cgSzy5ZcPhsKBNagAGQaMA In-Reply-To: <2025.1202488530@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/105 X-Sequence-Number: 28179 The doc says to do an initdb and reload the data whenever you run pg_resetxlog. Do you concur with that even if we are only resetting the OID counter? -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Friday, February 08, 2008 11:36 AM To: Mark Steben Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error on CLUSTER command "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