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

Re: pg_ctl vs. Windows locking

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>,"pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: pg_ctl vs. Windows locking
Date: 2004-06-14 15:42:41
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34BC60@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
> >>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 :-(

It is them. I observed the same thing, and verified taht it was the
pgstats procs.


//Magnus

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2004-06-14 15:55:50
Subject: Re: pg_ctl vs. Windows locking
Previous:From: Andrew DunstanDate: 2004-06-14 15:35:41
Subject: Re: pg_ctl vs. Windows locking

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