Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
Cc: "Steve McWilliams" <smcwilliams(at)EmprisaNetworks(dot)com>,pgsql-bugs(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org,"PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [PATCHES] [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1
Date: 2004-09-06 23:57:42
Message-ID: 22964.1094515062@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers-win32pgsql-patches
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> [ 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?

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Christopher Kings-LynneDate: 2004-09-07 03:04:56
Subject: Re: Permissions problem with sequences
Previous:From: Tom LaneDate: 2004-09-06 19:33:46
Subject: Re: BUG #1241: returns different result for the same result with differnt plans.

pgsql-hackers-win32 by date

Next:From: Magnus HaganderDate: 2004-09-07 08:13:53
Subject: Re: [PATCHES] [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1
Previous:From: Andreas PflugDate: 2004-09-06 22:01:56
Subject: Re: VC++ psql build broken

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2004-09-07 04:00:00
Subject: new spanish translations
Previous:From: Tom LaneDate: 2004-09-06 16:48:23
Subject: Re: fix for pg_dump (caused by array output syntax changes)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group