From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Deroshia <jeff(at)hal(dot)physast(dot)uga(dot)edu> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: postmaster does not shut down |
Date: | 2004-05-01 04:08:00 |
Message-ID: | 10278.1083384480@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Jeff Deroshia <jeff(at)hal(dot)physast(dot)uga(dot)edu> writes:
> I'm running PostgreSQL 7.4 on Mac OS X server 10.3.3. When I try
> pg_ctl stop as the postgres user, it times out waiting for postmaster
> to shut down, gives a failed error, then: pg_ctl: postmaster does not
> shut down
> The only thing I'm able to do is kill -9 <pid> then rm the pid file.
> This is not very good. Anyone know what would keep postmaster from
> shutting down?
A persistent client connection. If you want to kick out active clients,
you need (IIRC) "-m fast" option to pg_ctl stop.
In any case, "kill -9" on the postmaster is a particularly horrid idea
on OSX, because there's no way to clean up the leftover shared memory
segment (since Apple doesn't provide ipcrm). My experience is that you
have to reboot to get rid of the old shmem seg if you do this. Pretend
you never learned that command, and find an alternative.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Hampl | 2004-05-01 10:16:35 | Re: Query does not use index |
Previous Message | Adam Witney | 2004-04-30 18:17:44 | Re: Finding out db size... |