From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Trevor Talbot <quension(at)gmail(dot)com>, PostgreSQL <pgsql-general(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] 8.2.3: Server crashes on Windows using Eclipse/Junit |
Date: | 2007-10-22 20:45:02 |
Message-ID: | 471D0BCE.8020100@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> I was planning to make it even easier and let Windows do the job for us,
>> just using RegisterWaitForSingleObject(). Does the same - one thread per
>> 64 backends, but we don't have to deal with the queueing ourselves.
>> Should be rather trivial to do.
>
> How can that possibly work? Backends have to be able to run
> concurrently, and I don't see how they'll do that if they share a stack.
We're not talking about the backends, we're talking about the backend
waiter threads whose sole purpose is to wait for a backend to die and
then raise a signal when it does. We can easily have the kernel wait for
a whole bunch of them at once, and have it call our callback function
whenever anyone of them dies.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2007-10-22 20:47:10 | Re: Bitmap Heap scan 8.1/8.2 |
Previous Message | Trevor Talbot | 2007-10-22 20:44:29 | Re: [HACKERS] 8.2.3: Server crashes on Windows using Eclipse/Junit |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-22 21:05:21 | Re: rolcanlogin vs. the flat password file |
Previous Message | Trevor Talbot | 2007-10-22 20:44:29 | Re: [HACKERS] 8.2.3: Server crashes on Windows using Eclipse/Junit |