X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id BA8B89DCC22 for ; Wed, 21 Dec 2005 18:22:16 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27597-07 for ; Wed, 21 Dec 2005 18:22:18 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id D4D769DCC44 for ; Wed, 21 Dec 2005 18:22:14 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id jBLMMCF7025635 for ; Wed, 21 Dec 2005 22:22:12 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id jBLMIvZx016459 for pgsql-admin@postgresql.org; Wed, 21 Dec 2005 22:18:57 GMT (envelope-from news) From: "Qingqing Zhou" X-Newsgroups: pgsql.admin Subject: Re: PostgreSQL crashing Date: Wed, 21 Dec 2005 17:19:45 -0500 Organization: Hub.Org Networking Services Lines: 17 Message-ID: References: <4301.138.23.210.20.1135194176.squirrel@www.cs.ucr.edu> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=-1.366 required=5 tests=[ALL_TRUSTED=-1.44, AWL=0.074] X-Spam-Score: -1.366 X-Spam-Level: X-Archive-Number: 200512/257 X-Sequence-Number: 19977 wrote > > PostgreSQL runs for a while but always eventually (30min - 2hrs) crashes. > I thought it was memory initially but Memtest had no errors after running > for a day. I don't think it is a hardware issues because I can run other > applications without error. I have ran both version 8.0.3 and 8.1.1 with > the same error. It looks like a kernel bug or maybe a hardware problem to me. Other aplications doesn't crash maybe because they don't exercise this chunk of code that intensively. What's the elog information on postgres side? Regards, Qingqing