X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 81527D1DF59 for ; Wed, 11 Feb 2004 16:21:30 +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 82988-03 for ; Wed, 11 Feb 2004 12:21:16 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id E1FA3D1CE3E for ; Wed, 11 Feb 2004 12:21:16 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1BGLFDD021547; Wed, 11 Feb 2004 11:21:15 -0500 (EST) To: Mark Lubratt Cc: pgsql-admin@postgresql.org Subject: Re: IDE and write cache In-reply-to: <7FADF594-5C59-11D8-9292-000A9579AF50@indeq.com> References: <7FADF594-5C59-11D8-9292-000A9579AF50@indeq.com> Comments: In-reply-to Mark Lubratt message dated "Wed, 11 Feb 2004 00:14:07 -0600" Date: Wed, 11 Feb 2004 11:21:14 -0500 Message-ID: <21546.1076516474@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/162 X-Sequence-Number: 12336 Mark Lubratt writes: > You mentioned that you'd see the problem during a large number of > concurrent transactions. My question is, is this a necessary condition > for the database crashing when the plug was pulled, or did you need use > a large number of concurrent transactions to "guarantee" that when you > pulled the plug, that it would be at an inopportune time? In other > words, is an IDE drive still "more" susceptible to a power outage > problem even under light load? A heavy load makes it more likely that you'd see the problem, but only because it improves the odds that there will be data "in flight" at the instant the power drops. You can still lose on a lightly loaded system if your luck is bad. regards, tom lane