| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Greg Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: windows shared memory error |
| Date: | 2009-05-01 10:23:18 |
| Message-ID: | 937d27e10905010323y5e21eca2l8e0fc798bd22194b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 1, 2009 at 11:05 AM, Greg Stark <stark(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-05-01 12:49:47 | ECPG, two varchars with same name on same line |
| Previous Message | Pavel Stehule | 2009-05-01 10:16:37 | Re: plpgsql's EXIT versus block and loop nesting |