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 F153D5389A for ; Mon, 11 Apr 2005 12:15:43 -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 57285-09 for ; Mon, 11 Apr 2005 15:15:38 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by svr1.postgresql.org (Postfix) with ESMTP id 45475538C1 for ; Mon, 11 Apr 2005 12:15:37 -0300 (ADT) Received: by rproxy.gmail.com with SMTP id j1so1152236rnf for ; Mon, 11 Apr 2005 08:15:37 -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=c0NjS+bhhUH72x53FBJ1xHR1OULjrVxETqXXLDrsMmzflqG5KdVjrJKvihHe4AtZqUvprFGO5GOrn1bOSRrPz3MKOfKjO4MhGB2Jn4N2bL4j9nIy1XoAxH8eYWPcZG2jZtHoHB0wHz2J41xPDj1BE/R7dG9E9KJjMgbls7zpiZw= Received: by 10.39.3.56 with SMTP id f56mr2862593rni; Mon, 11 Apr 2005 08:15:36 -0700 (PDT) Received: by 10.38.97.43 with HTTP; Mon, 11 Apr 2005 08:15:36 -0700 (PDT) Message-ID: <674d1f8a05041108154d08f587@mail.gmail.com> Date: Mon, 11 Apr 2005 20:45:36 +0530 From: Gourish Singbal Reply-To: Gourish Singbal To: Don Drake Subject: Re: Server crashing Cc: Tom Lane , pgsql-performance@postgresql.org In-Reply-To: <6c21003b0504110724711a9685@mail.gmail.com> 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> <6c21003b0504110724711a9685@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.258 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/216 X-Sequence-Number: 11613 by Truncating the serverlog do you mean the data_log (as in my case) log file of the postgresql sever ?. If thats the file you truncated than i think its not a good habit..since you might need it at some point of time for some debugging purpose in production. You could use something like assuming there is a dummy file of 0 bytes in logs folder.. cp data_log data_log_$current_time cat logs/dummy_file>data_log gzip data_log_$current_time mv data_log_$current_time.gz logs/data_log_$current_time.gz Hope this helps Best Gourish Singbal On Apr 11, 2005 7:54 PM, Don Drake wrote: > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match > -- Best, Gourish Singbal