Re: windows shared memory error - Mailing list pgsql-hackers

From Dave Page
Subject Re: windows shared memory error
Date
Msg-id 937d27e10905010323y5e21eca2l8e0fc798bd22194b@mail.gmail.com
Whole thread Raw
In response to Re: windows shared memory error  (Greg Stark <stark@enterprisedb.com>)
List pgsql-hackers
On Fri, May 1, 2009 at 11:05 AM, Greg Stark <stark@enterprisedb.com> wrote:

> Do we have any idea why "it may take a short while before it gets
> dropped from the global namespace"? Is there some demon running which
> only wakes up periodically? Or any specific reason it takes so long?
> That might give us a clue exactly how long to sleep for.

I can't find any info in a quick search. I don't see offhand why it
would take time - it's just reference counting handles held by
different processes.

> Is there any way to tell Windows to wake up and do its job? Or to
> block until its done?

Not that I'm aware of.


-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: plpgsql's EXIT versus block and loop nesting
Next
From: Greg Stark
Date:
Subject: Re: Restore deleted rows