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 8F3623A4157 for ; Mon, 25 Oct 2004 19:48:25 +0100 (BST) 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 05932-08 for ; Mon, 25 Oct 2004 18:48:15 +0000 (GMT) Received: from bandit.Colorado.EDU (bandit.colorado.edu [128.138.129.126]) by svr1.postgresql.org (Postfix) with ESMTP id 80A683A419B for ; Mon, 25 Oct 2004 19:48:15 +0100 (BST) Received: from colorado.edu (comp113-238-dhcp.colorado.edu [128.138.113.238]) by bandit.Colorado.EDU (8.12.10/8.12.10/ITS-6.0/test) with ESMTP id i9PImFOU003688 for ; Mon, 25 Oct 2004 12:48:15 -0600 (MDT) Message-ID: <417D4A96.2040109@colorado.edu> Date: Mon, 25 Oct 2004 12:48:54 -0600 From: Andy Marangakis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: runaway processes, data corruption Content-Type: multipart/alternative; boundary="------------010206080903040205070102" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=HTML_20_30, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: * X-Archive-Number: 200410/380 X-Sequence-Number: 15373 This is a multi-part message in MIME format. --------------010206080903040205070102 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi all, I've encounter a couple of bugaboos recently in a production database I run (7.3.4 on Solaris 8). One is that killing a query from a client tool such as dbVisualizer can cause the process on the server to become a runaway, consuming CPU and causing other processes to go into a TIME_WAIT state. The other is that a spontaneous reboot of the server (unknown cause, some hardware/OS wierdness) caused a catastrophic corruption, requiring rebuild from backup. The error returned was: PANIC: Invalid page header in block 2462 of 1365344463 I've upgraded to 7.4 in hopes that crash resistance improves. Any other thoughts on protecting against such occurances in the future? Thanks in advance. _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Andy Marangakis 303-492-0527 Database Administrator 303-492-4198 fax Information Technology Services University of Colorado at Boulder --------------010206080903040205070102 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all,
I've encounter a couple of bugaboos recently in a production database I run (7.3.4 on Solaris 8). One is that killing a query from a client tool such as dbVisualizer can cause the process on the server to become a runaway, consuming CPU and causing other processes to go into a TIME_WAIT state. The other is that a spontaneous reboot of the server (unknown cause, some hardware/OS wierdness) caused a catastrophic corruption, requiring rebuild from backup. The error returned was:

    PANIC: Invalid page header in block 2462 of 1365344463

I've upgraded to 7.4 in hopes that crash resistance improves. Any other thoughts on protecting against such occurances in the future? Thanks in advance.

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Andy Marangakis                                   303-492-0527
Database Administrator                            303-492-4198 fax
Information Technology Services
University of Colorado at Boulder

--------------010206080903040205070102--