Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 5F35A1337B50 for ; Tue, 26 Oct 2010 02:34:04 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 93850-03 for ; Tue, 26 Oct 2010 05:33:57 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from rs73.luxsci.com (rs73.luxsci.com [64.49.254.135]) by mail.postgresql.org (Postfix) with ESMTP id 39D081337999 for ; Tue, 26 Oct 2010 02:33:56 -0300 (ADT) Received: from GNANAM (ABTS-TN-Static-186.58.165.122.airtelbroadband.in [122.165.58.186] (may be forged)) (authenticated bits=0) by rs73.luxsci.com (8.13.8/8.13.8) with ESMTP id o9Q5XnQj024016; Tue, 26 Oct 2010 00:33:52 -0500 Reply-To: From: "Gnanakumar" To: "'Greg Smith'" Cc: References: <001201cb0321$df429d40$9dc7d7c0$@com> <00ca01cb03dc$a9ffe780$fdffb680$@com> <002d01cb7417$595f78d0$0c1e6a70$@com> <4CC5A0C6.8080901@2ndquadrant.com> In-Reply-To: <4CC5A0C6.8080901@2ndquadrant.com> Subject: Re: pg_ctl: server does not shut down Date: Tue, 26 Oct 2010 11:02:06 +0530 Organization: Zoniac Software Private Limited Message-ID: <002701cb74cf$23607f50$6a217df0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Act0WHzNciMz3UapRaiOosVWz/QYHQAc+Plg Content-Language: en-us X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.914 tagged_above=-10 required=5 tests=BAYES_05=-0.5, MAY_BE_FORGED=1.414 X-Spam-Level: X-Archive-Number: 201010/182 X-Sequence-Number: 35923 > You can check if PITR is disabled by executing: > SHOW archive_command; > At a psql prompt. If that's empty, then you turned it off, and it isn't involved in the shutdown issue you have anymore. Yes, I could see empty value here. > Take a look at what processes are still running against the database and see if there are clients attached after the fast shutdown attempt. > If so, those are your problem, not something to PITR. Yes, I can see the following processes still running. I used the command 'ps -ef |grep postgres' to list. postgres 3376 1 0 07:20 ? 00:00:00 /mnt/database/pgsql/bin/postgres -D /usr/local/pgsql/data postgres 3381 3376 0 07:20 ? 00:00:00 postgres: logger process postgres 3383 3376 0 07:20 ? 00:00:00 postgres: writer process But why logger and writer process are still running/showing up here for a very long time after issuing 'service postgresql stop'. What could be the problem? Also, am sure here that no other clients (database connections) are connected at this time.