X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1EC58D1DE65 for ; Fri, 16 Jan 2004 15:56:17 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 01567-08 for ; Fri, 16 Jan 2004 11:55:50 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id F1D9BD1DF84 for ; Fri, 16 Jan 2004 11:55:45 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0GFtopH000115; Fri, 16 Jan 2004 10:55:50 -0500 (EST) To: cgg007@yahoo.com Cc: pgsql-admin@postgresql.org Subject: Re: Protect pg_xlog ? In-reply-to: <20040116133417.97868.qmail@web13807.mail.yahoo.com> References: <20040116133417.97868.qmail@web13807.mail.yahoo.com> Comments: In-reply-to Chris Gamache message dated "Fri, 16 Jan 2004 05:34:17 -0800" Date: Fri, 16 Jan 2004 10:55:50 -0500 Message-ID: <114.1074268550@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/135 X-Sequence-Number: 11998 Chris Gamache writes: > It might not matter one bit that the actual data files are safe and > sound if the transaction log is corrupted. There's always pg_resetxlog. However, if you value data integrity over performance, it'd probably be better to have data+log on one redundant array than to have data on a redundant array and log on a single nonredundant disk. regards, tom lane