Re: pg_ctl vs. Windows locking

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers-win32 <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: pg_ctl vs. Windows locking
Date: 2004-06-14 15:18:38
Message-ID: 384.1087226318@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> When I was watching it in the Task Manager, it was observable that the
> postmaster exited before some of the other backend processes, by up to a
> second or two.

The stats collector processes normally don't shut down until they
observe postmaster exit (and I think in CVS tip there's an
up-to-one-second delay before they'll even look). Everything else
should be gone first though.

regards, tom lane

In response to

Responses

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Andrew Dunstan 2004-06-14 15:35:41 Re: pg_ctl vs. Windows locking
Previous Message Andrew Dunstan 2004-06-14 14:54:02 Re: pg_ctl vs. Windows locking