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 EA3A55368E for ; Mon, 11 Apr 2005 11:24:24 -0300 (ADT) 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 39721-05 for ; Mon, 11 Apr 2005 14:24:15 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by svr1.postgresql.org (Postfix) with ESMTP id 1D04D5321B for ; Mon, 11 Apr 2005 11:24:14 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 67so2803071wri for ; Mon, 11 Apr 2005 07:24:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=XJkR1HxZPIBfdbSocZpXB2cW4IjK6Z2BNEiRY+VETujdW8nn7TIMDf+Y4R2B2vE5vmweTdbdfql79X90cMbwfSNpe4ytPEIOMsoMqiB1owKaO+sg70E8Dn5IVf2JWUri5gwrOTtox/odDkc5JOE1OI6kJQqPv3SbzdZuo/ZN5MU= Received: by 10.54.21.37 with SMTP id 37mr2144227wru; Mon, 11 Apr 2005 07:24:18 -0700 (PDT) Received: by 10.54.97.13 with HTTP; Mon, 11 Apr 2005 07:24:18 -0700 (PDT) Message-ID: <6c21003b0504110724711a9685@mail.gmail.com> Date: Mon, 11 Apr 2005 09:24:18 -0500 From: Don Drake Reply-To: Don Drake To: Tom Lane Subject: Re: Server crashing Cc: pgsql-performance@postgresql.org In-Reply-To: <22320.1113200965@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <6c21003b05041020166d32111c@mail.gmail.com> <22320.1113200965@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.218 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/215 X-Sequence-Number: 11612 Well, a vacuum on the entire DB seemed to have cleaned things up. No other user was logged into the server, and I certainly did not send the signal. I did clean up the serverlog file by truncating it ( > serverlog) while the DB was running, I don't think it liked that since it crashed the DB. I've done this on my Linux server many times and it never complained. I won't be doing that again. -Don On Apr 11, 2005 1:29 AM, Tom Lane wrote: > Don Drake writes: > > My server is crashing on a delete statement. > > Here's the error message in the log file: > > > LOG: 00000: received fast shutdown request > > LOCATION: pmdie, postmaster.c:1736 > > That says that something sent the postmaster a SIGINT signal. > I think it's highly unlikely that the DELETE statement did it. > > regards, tom lane > -- Donald Drake President Drake Consulting http://www.drakeconsult.com/ http://www.MailLaunder.com/ http://www.mobilemeridian.com/ 312-560-1574