Hi Tom, > Have you looked into the postmaster log to see > *why* it's not shutting down?
I did tail on the log and got... [2008-03-24 14:31:39.331 PDT] < 11148 2008-02-26 18:15:00 PST >LOG: received smart shutdown request [2008-03-24 14:31:39.331 PDT] < 29578 2008-03-24 06:38:33 PDT >LOG: autovacuum launcher shutting down [2008-03-24 14:32:58.740 PDT] < 11148 2008-02-26 18:15:00 PST >LOG: received fast shutdown request [2008-03-24 14:46:03.123 PDT] <postgres 8619 127.0.0.1 2008-03-24 14:46:03 PDT /usr/local/pgsql/bin/postgres>FATAL: the database system is shutting down [2008-03-24 15:52:43.520 PDT] <michaelstevens 11367 [local] 2008-03-24 15:52:43 PDT /usr/local/pgsql/bin/postgres>FATAL: the database system is shutting down [2008-03-24 15:52:43.563 PDT] <michaelstevens 11368 [local] 2008-03-24 15:52:43 PDT /usr/local/pgsql/bin/postgres>FATAL: the database system is shutting down I am about to try: pg_ctl stop -m immediate Regards, Tena Sakai -----Original Message----- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Mon 3/24/2008 3:11 PM To: Tena Sakai Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] it refuses to go down... "Tena Sakai" <[EMAIL PROTECTED]> writes: > $ pg_ctl stop -m fast > waiting for server to shut > down............................................................... failed > pg_ctl: server does not shut down Have you looked into the postmaster log to see *why* it's not shutting down? > Can I kill the process 11148 and do as I planned accordingly? It's not exactly recommended when you don't know what the problem is. Killing only the postmaster and not its child processes is especially not recommended --- there are some defenses in place against that, but nothing that can't be broken by a sufficiently determined DBA. regards, tom lane
