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 7A754D1B7E7 for ; Fri, 16 Jan 2004 13:34:46 +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 40159-06 for ; Fri, 16 Jan 2004 09:34:18 -0400 (AST) Received: from web13807.mail.yahoo.com (web13807.mail.yahoo.com [216.136.175.17]) by svr1.postgresql.org (Postfix) with SMTP id 4659ED1D576 for ; Fri, 16 Jan 2004 09:34:14 -0400 (AST) Message-ID: <20040116133417.97868.qmail@web13807.mail.yahoo.com> Received: from [216.173.173.66] by web13807.mail.yahoo.com via HTTP; Fri, 16 Jan 2004 05:34:17 PST Date: Fri, 16 Jan 2004 05:34:17 -0800 (PST) From: Chris Gamache Reply-To: cgg007@yahoo.com Subject: Protect pg_xlog ? To: pgsql-admin@postgresql.org In-Reply-To: <35ACCBB8-47BD-11D8-B6AB-000393D4C9F2@smcm.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/131 X-Sequence-Number: 11994 I have one RAID 1+0 array available. My primary concern is data integrity. The general instruction is to put pg_xlog on another filesystem, seperated physically from the database files, for maximum performance. That is what I had planned on doing. However, it dawned on me that there could be a serious problem if the pg_xlog got corrupted or was lost in a hardware failure. It might not matter one bit that the actual data files are safe and sound if the transaction log is corrupted. Is protecting pg_xlog as important as protecting the rest of the data files? Will the performance hit, which happens when one keeps pg_xlog on the same filesystem as the database, be substantial enough to warrant spending more money on another array of drives to use for pg_xlog? CG __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus