Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 24 Oct 2005 11:14:04 -0400
- Message-id: <4014(dot)1130166844(at)sss(dot)pgh(dot)pa(dot)us>
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
- References:
- Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- From: Merlin Moncure
- Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- From: Tom Lane
- Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- From: Andrew Dunstan
- Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- Prev by Date: Re: libpq's pollution of application namespace
- Next by Date: Re: LISTEN/NOTIFY enhancement: Portable signal handling?
- Previous by thread: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- Next by thread: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
- Indexes: