Re: [pgsql-hackers-win32] [BUGS] Win32 deadlock detection not working for Postgres8beta1 - Mailing list pgsql-patches

From Magnus Hagander
Subject Re: [pgsql-hackers-win32] [BUGS] Win32 deadlock detection not working for Postgres8beta1
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE475C02@algol.sollentuna.se
Whole thread Raw
Responses Re: [pgsql-hackers-win32] [BUGS] Win32 deadlock detection not working for Postgres8beta1
List pgsql-patches
> > [ fix broken CHECK_FOR_INTERRUPTS macro ]
>
> Applied.  I see how this might change detection of
> statement_timeout, but I do not actually see what it's got to
> do with deadlock detection.
> In the deadlock situation the process that needs to wake up
> is going to be blocked on a semaphore, and so it's not going
> to be executing CHECK_FOR_INTERRUPTS at all.  How does this
> fix that case?

It doesn't. This is why the second version of the patch was required,
per http://archives.postgresql.org/pgsql-patches/2004-09/msg00039.php.
It even specifically says this is so it fixes the deadlock issues and
not just statement_timeout :-)


//Magnus

pgsql-patches by date:

Previous
From: Weiping
Date:
Subject: Re: fix for pg_dump (caused by array output syntax changes)
Next
From: Tom Lane
Date:
Subject: Re: [pgsql-hackers-win32] [BUGS] Win32 deadlock detection not working for Postgres8beta1