X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 6C2D69FA502 for ; Mon, 17 Jul 2006 14:40:55 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 38919-07 for ; Mon, 17 Jul 2006 14:40:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D05AC9FA418 for ; Mon, 17 Jul 2006 14:40:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6HHejj9004452; Mon, 17 Jul 2006 13:40:45 -0400 (EDT) To: "Mr. Dan" cc: pgsql-admin@postgresql.org Subject: Re: On-line backup In-reply-to: References: Comments: In-reply-to "Mr. Dan" message dated "Mon, 17 Jul 2006 13:15:07 -0400" Date: Mon, 17 Jul 2006 13:40:45 -0400 Message-ID: <4451.1153158045@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/146 X-Sequence-Number: 22392 "Mr. Dan" writes: > Is this 2003 advice still relevant with postgresql 8.1.0? Our b-tree > indexes corrupt pretty often on our production server running 8.1.0 and we > are grasping for a solution. Corrupt how --- what's the exact symptoms? The *first* bit of advice I'd give you is that you shouldn't be on 8.1.0 anymore. We don't make update releases just for amusement. However, whether this represents an already-fixed problem is impossible to tell with no details. (As for that 2003 discussion, that predates the availability of PITR. Now, you can use a plain tar backup ... as long as you've got WAL logs to go with it.) regards, tom lane