Skip site navigation (1) Skip section navigation (2)

Re: pg_ctl vs. Windows locking

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-hackers-win32 <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: pg_ctl vs. Windows locking
Date: 2004-06-14 15:35:41
Message-ID: 40CDC5CD.30806@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
Tom Lane wrote:

>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.
>
>  
>

I assumed it was them. Can't tell in Task Manager, that I can see - all 
you get is the image name :-(

Sounds like a 2 second sleep should do the trick. Will test later.

Maybe we should do it everywhere, not just Windows, to ensure that we 
don't get nasty interleaving on the log file?

cheers

andrew

In response to

Responses

pgsql-hackers-win32 by date

Next:From: Magnus HaganderDate: 2004-06-14 15:42:41
Subject: Re: pg_ctl vs. Windows locking
Previous:From: Tom LaneDate: 2004-06-14 15:18:38
Subject: Re: pg_ctl vs. Windows locking

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group