Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
Date: 2005-10-24 15:14:04
Message-ID: 4014.1130166844@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> We might be able to solve that for plpgsql, but in general we can't,
> ISTM. What if I write a plperl function that loops forever? We have no
> chance there to call CHECK_FOR_INTERRUPTS.

Yeah, I was thinking about that too. Still, we can/should/already did
fix it in plpgsql.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zygo Blaxell 2005-10-24 16:02:11 Re: LISTEN/NOTIFY enhancement: Portable signal handling?
Previous Message Bruce Momjian 2005-10-24 15:11:47 Re: libpq's pollution of application namespace