Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 8412F9F9C35 for ; Wed, 6 Dec 2006 02:20:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 95310-01 for ; Wed, 6 Dec 2006 02:20:31 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.237]) by postgresql.org (Postfix) with ESMTP id 0E6249F931B for ; Wed, 6 Dec 2006 02:20:31 -0400 (AST) Received: by qb-out-0506.google.com with SMTP id e21so1978343qba for ; Tue, 05 Dec 2006 22:20:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=TurJ0+P87dNZ+NZMhrbGU7egTazLTTOy8XSXAnGJpzeSVet8mwK+owxpCQxAy/exBI79i8+HiEcvwhwL/rbqdaYKcaU+CqCWPh3+XdA1u/i7wy5RKSdP/uqVS7zXiF+cGy70682eLKB6MRM9jyvOxsFdljwAqt7A4Cx2evKh1Xo= Received: by 10.35.121.9 with SMTP id y9mr663273pym.1165386030476; Tue, 05 Dec 2006 22:20:30 -0800 (PST) Received: by 10.35.80.8 with HTTP; Tue, 5 Dec 2006 22:20:30 -0800 (PST) Message-ID: Date: Wed, 6 Dec 2006 11:50:30 +0530 From: "Rajesh Kumar Mallah" To: "Tom Lane" Subject: Re: Restart time Cc: pgsql-performance@postgresql.org In-Reply-To: <10203.1165347590@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13399_16294122.1165386030432" References: <4575A78F.5040504@inrialpes.fr> <8738.1165342609@sss.pgh.pa.us> <10203.1165347590@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/106 X-Sequence-Number: 22162 ------=_Part_13399_16294122.1165386030432 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 12/6/06, Tom Lane wrote: > > "Rajesh Kumar Mallah" writes: > > Startup time of a clean shutdown database is constant. But we still > > face problem when it comes to shutting down. PostgreSQL waits > > for clients to finish gracefully. till date i have never been able to > > shutdown > > quickly (web application scenerio) and i tend to do pg_ctl -m immediate > stop > > mostly. > > RTFM ... you should be using -m fast not -m immediate. -m immediate > is for emergency situations not routine. Thanks for correcting , -m fast works fine for me. I shall RTFM..... :) Regds mallah. regards, tom lane ------=_Part_13399_16294122.1165386030432 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 12/6/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Rajesh Kumar Mallah" <mallah.rajesh@gmail.com> writes:
> Startup time of a clean shutdown database is constant. But we still
> face problem when it comes to shutting down. PostgreSQL waits
> for clients to finish gracefully. till date i have never been able to
> shutdown
> quickly (web application scenerio) and i tend to do pg_ctl -m immediate stop
> mostly.

RTFM ... you should be using -m fast not -m immediate.  -m immediate
is for emergency situations not routine.

Thanks for correcting , -m fast  works fine for me.
I shall RTFM..... :)
Regds
mallah.                        regards, tom lane

------=_Part_13399_16294122.1165386030432--