From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | ohp(at)pyrenet(dot)fr |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unixware 714 pthreads |
Date: | 2004-10-27 18:53:26 |
Message-ID: | 200410271853.i9RIrQk07419@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
ohp(at)pyrenet(dot)fr wrote:
> Dear Bruce,
>
> Thanks for your reply, I was desperate I did'nt get one!
>
> As I said, I'm quite sure there is a bug in pthread library, Before saying
> this to SCO, I have to prove it. Postgresql is the way to prove it!
>
> What I need is to know where to start from (I'd like to put elogs where
> statement_timeout is processed to see what really happens and why it
> doesn't cancel the query).
>
> Could someone tell me where to look for? If anyone is interessed in
> debugging this issue with me, I can set up an account on a test unixware
> machine.
My guess is that there is some problem with delivering alarm signals
because that is how the timeout code works.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-10-27 19:13:44 | Re: [HACKERS] src/timezone/pgtz __imp__my_exec_path |
Previous Message | Magnus Hagander | 2004-10-27 18:25:45 | Re: [HACKERS] src/timezone/pgtz __imp__my_exec_path |