X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9183A5E487A for ; Mon, 6 Sep 2004 03:18:08 +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 16991-10 for ; Mon, 6 Sep 2004 02:18:07 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 6F0615E47FE for ; Mon, 6 Sep 2004 03:18:05 +0100 (BST) 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 i862I6fP003780; Sun, 5 Sep 2004 22:18:06 -0400 (EDT) To: Martin Foster Cc: pgsql-performance@postgresql.org Subject: Re: Tanking a server with shared memory In-reply-to: References: Comments: In-reply-to Martin Foster message dated "Mon, 06 Sep 2004 01:15:24 +0000" Date: Sun, 05 Sep 2004 22:18:05 -0400 Message-ID: <3779.1094437085@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/35 X-Sequence-Number: 8163 Martin Foster writes: > While I know this is a Perl issue, but figured I might be able to gain > some insight on how a server could drop without at least generating a > panic. Any ideas? The standard spelling for this is "kernel bug". Send a reproducible example to the OpenBSD kernel maintainers. regards, tom lane