Tom Lane wrote:
>"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
>
>
>>3. A pl/pgsql function stuck in a empty loop is unkillable except by
>>killing the process on the server, which cycles the entire server. This
>>was the behavior before the patch, btw.
>>
>>
>
>Hmm, that suggests we need another CHECK_FOR_INTERRUPTS somewhere in
>plpgsql. Please show the exact test case you were using.
>
>
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.
cheers
andrew