X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2D15156530 for ; Fri, 11 Mar 2005 00:04:31 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 09446-02 for ; Fri, 11 Mar 2005 00:04:30 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id B6C935650E for ; Fri, 11 Mar 2005 00:04:28 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2B04Tc9027056; Thu, 10 Mar 2005 19:04:29 -0500 (EST) To: Alex Turner Cc: pgsql-admin@postgresql.org, Alex Turner Subject: Re: IO Timeout In-reply-to: <33c6269f050310111892ae175@mail.gmail.com> References: <33c6269f050310111892ae175@mail.gmail.com> Comments: In-reply-to Alex Turner message dated "Thu, 10 Mar 2005 14:18:35 -0500" Date: Thu, 10 Mar 2005 19:04:29 -0500 Message-ID: <27055.1110499469@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/163 X-Sequence-Number: 16661 Alex Turner writes: > I have a question about IO timeouts: > We are using the 3ware escalade 9500S series of cards, and we had a > drive failure this morning. Apparnetly the card waits 30 seconds for > the drive to respond, and if it doesn't, it put's the drive in a fail > state. Postgres it seems didn't wait 30 seconds before it decided > that the system was upset, and put the database in maintainence mode. > Is there a way to increase to IO wait timeout so this doesn't happen? Postgres hasn't got any "IO timeouts". Your concern would be better directed to whatever kernel you're using; any sort of timeout on a disk operation would be happening at the kernel level. For that matter, Postgres hasn't got any concept of "putting the database in maintainence mode", so you haven't described what happened very accurately at all. regards, tom lane