Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2BEA12E01D9 for ; Fri, 8 Feb 2008 15:49:55 -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 72487-09 for ; Fri, 8 Feb 2008 15:49:52 -0400 (AST) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by postgresql.org (Postfix) with ESMTP id B317B2E0172 for ; Fri, 8 Feb 2008 15:49:51 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so739658waf.5 for ; Fri, 08 Feb 2008 11:49:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=FotRttcU7iuCnI1585ZCkTxcyIRQvSosQQU3y1lMcWM=; b=adBjNjuMy8y3jAiK7yYH7COLBixm7l3a/6YiPz6zhJ7MB1jSZodN6rfOLaBOfEG2Nm+zWg/XM6esxbkIN563D5qIEFQ4DpQv9GXMHr+hyXB9vZCe2iTlb911Nk7thQZTKgDo3noqjegdDQoyhBHP45t0w28J+aI2vuVIBv9IC5g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CroOVSfsB7xYjqUf6qiUfgr+Joo2e/aGsN2ERnSpYXrM8/WHIe/o9EJbZw2++8VPajccYMV4FAfkpfTDQSS2JBdqSNvkL4GJxkNNqkQSSd8E51KZjN0bNTmB3ihFzJ6FAmAGAm3hQ/rtsRHUJZ7uX/CipznkudevBnAgbiPjfx4= Received: by 10.115.110.6 with SMTP id n6mr5846661wam.92.1202500190775; Fri, 08 Feb 2008 11:49:50 -0800 (PST) Received: by 10.114.131.4 with HTTP; Fri, 8 Feb 2008 11:49:50 -0800 (PST) Message-ID: Date: Fri, 8 Feb 2008 13:49:50 -0600 From: "Scott Marlowe" To: "Mark Steben" Subject: Re: Error on CLUSTER command Cc: "Tom Lane" , pgsql-admin@postgresql.org In-Reply-To: <00bf01c86a89$fa4af7a0$14010a0a@dei26g028575> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2025.1202488530@sss.pgh.pa.us> <00bf01c86a89$fa4af7a0$14010a0a@dei26g028575> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/106 X-Sequence-Number: 28180 On Feb 8, 2008 1:37 PM, Mark Steben wrote: > 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? On 7.4 I'd say you'd be better off dumping and reloading all your data than playing with pg_resetxlog on a live database. Might as well update to 7.4.19 while you're at it. I'd run a dump restore to a test machine running 7.4.19 first to make sure it will go well, or get another server that can handle the load, or make a new 7.4.19 instance on the same machine and transfer to that. But if it's a production database I wouldn't run pg_resetxlog on it myself.