Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 38289133655C for ; Tue, 18 Jan 2011 01:27:55 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 36786-04 for ; Tue, 18 Jan 2011 05:27:47 +0000 (UTC) X-Greylist: delayed 00:06:33.861001 by SQLgrey-1.7.6 Received: from rs73.luxsci.com (rs73.luxsci.com [64.49.254.135]) by mail.postgresql.org (Postfix) with ESMTP id 7E8EE1337B39 for ; Tue, 18 Jan 2011 01:27:47 -0400 (AST) Received: from GNANAM ([180.151.61.10]) (authenticated bits=0) by rs73.luxsci.com (8.13.8/8.13.8) with ESMTP id p0I5L93R004697; Mon, 17 Jan 2011 23:21:11 -0600 Reply-To: From: "Gnanakumar" To: Subject: How do I stop/disable PITR and safely clean WAL segments? Date: Tue, 18 Jan 2011 10:48:13 +0530 Organization: Zoniac Software Private Limited Message-ID: <00fe01cbb6cf$1cb1a200$5614e600$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 thread-index: Acu2zxqIoXh+r0sTSVywc+voFv+OYg== Content-Language: en-us X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201101/104 X-Sequence-Number: 36544 Hi, Our production server is running PostgreSQL v8.2.3 on CentOS release 5.2 (Final). We've setup PITR in our production server. For some reasons, after setting up PITR, we're not able to manage and maintain it. Eventually, our WAL archive drive (secondary drive) has become full (100% use) and additional WAL archive segments that are to be archived got accumulated in pg_xlog/ directory itself (which is available in primary drive) PITR SETUP DETAILS There are 2 drives: 1. Primary drive (pgsql/data/ directory resides) is 400 GB. 2. Secondary drive (WAL archives) is 300 GB. All WAL archives are written to this secondary drive. Now, we've decided to stop/disable PITR. My question is, in this situation, how do I stop/disable PITR and safely clean up all WAL segments from both the drives? What are the recommended/suggested ways? Experts advice/idea/suggestion on this are highly appreciated. Regards, Gnanam