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 88A349DC82D for ; Mon, 16 Jan 2006 14:25:20 -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 08327-01 for ; Mon, 16 Jan 2006 14:25:12 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 650079DC82A for ; Mon, 16 Jan 2006 14:25:09 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0GINlIs010099; Mon, 16 Jan 2006 13:23:47 -0500 (EST) To: "Sally Sally" cc: ajs@crankycanuck.ca, pgsql-admin@postgresql.org Subject: Re: Unable to connect to a specific database In-reply-to: References: Comments: In-reply-to "Sally Sally" message dated "Mon, 16 Jan 2006 17:50:26 +0000" Date: Mon, 16 Jan 2006 13:23:47 -0500 Message-ID: <10098.1137435827@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.227 required=5 tests=[AWL=-0.049, MAILTO_TO_SPAM_ADDR=0.276] X-Spam-Score: 0.227 X-Spam-Level: X-Archive-Number: 200601/177 X-Sequence-Number: 20265 "Sally Sally" writes: > Well after kill -9, it was in recovery mode but I restarted the server > again. It took a while (~ 45min) but it connected again. I have noticed that > after a vacuum it takes a while to connect for the first time. You mentioned > kill -9 is very bad news. Everything seems to be working fine now, should I > be worried? What are the consequences? The problem with kill -9 is mainly if you use it to kill the postmaster; then the postmaster is unable to release its shared memory segment before quitting. Depending on how your kernel handles shared memory, the segment might stick around indefinitely (unless manually cleaned up or you reboot the whole machine). This will eventually run the system out of memory and/or prevent launching a new postmaster. kill -9 on an individual backend isn't so dangerous, but it's still using a steam hammer to swat a fly. Try less invasive methods first, like kill -INT (ie, query cancel). BTW, the unreasonably long restart time suggests that you've set unreasonably long inter-checkpoint intervals. Might want to think about backing off the checkpoint parameters a bit. regards, tom lane