Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id C59162E00B4 for ; Thu, 21 Feb 2008 19:11:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 31323-05 for ; Thu, 21 Feb 2008 19:11:51 -0400 (AST) Received: from mail.internode.com.au (mail.internode.com.au [192.83.231.27]) by postgresql.org (Postfix) with ESMTP id E99A32E00BD for ; Thu, 21 Feb 2008 19:11:56 -0400 (AST) Received: from [172.16.0.221] (staffnet.internode.com.au [203.26.95.65]) by mail.internode.com.au (8.13.7/8.12.1) with ESMTP id m1LNBoqN012407; Fri, 22 Feb 2008 09:41:51 +1030 (CST) Message-ID: <47BE0536.3080605@internode.com.au> Date: Fri, 22 Feb 2008 09:41:50 +1030 From: Shilpa Sudhakar User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: Andrew Sullivan , pgsql-admin@postgresql.org Subject: Re: pg_ctl reload query References: <47BD0C94.7010208@internode.com.au> <20080221170244.GL17293@crankycanuck.ca> In-Reply-To: <20080221170244.GL17293@crankycanuck.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on mail X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/255 X-Sequence-Number: 28329 Thanks for the reply. I am sure i didn't issue the restart command. i only did the reload. I'll find out from my other team mates if they issued any restart command by mistake. Thanks again. Regards, Shilpa Andrew Sullivan wrote: > On Thu, Feb 21, 2008 at 04:01:00PM +1030, Shilpa Sudhakar wrote: > >> Hi All, >> >> Wanted to know what does pg_ctl do in the background when we run *pg_ctl >> -D datadir reload * >> > > It sends a SIGHUP to the back end. > > >> command. Generally, it just reloads the files and everything works fine. >> But strangely, last time when we ran the reload command and tried to >> access *psql dbname, * >> It gives a message *"database shutting down" * >> > > Are you sure you didn't issue "restart" instead? It's an easy enough > mistake to make. > > A > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq >