Re: Converting pqsignal to void return

From: Paul Ramsey <pramsey(at)cleverelephant(dot)ca>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Subject: Re: Converting pqsignal to void return
Date: 2025-01-22 17:01:09
Message-ID: AD9CFCF4-B2AD-4138-8E69-76DB068873A3@cleverelephant.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Jan 22, 2025, at 8:50 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>> It is possible we have been Doing It Wrong all this time, and would love some pointers on the right way to do this.
>
> All your interrupt handler is doing "for you" is setting
> http_interrupt_requested, right? Why do you need that variable? Seems you
> could just check postgres' QueryCancelPending? And perhaps ProcDiePending, if
> you want to handle termination too.

This is the Knowledge that was sitting right in front of me, but I could not see.
From the road to Damascus,
Paul

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2025-01-22 17:05:13 Re: Quadratic planning time for ordered paths over partitioned tables
Previous Message Andres Freund 2025-01-22 17:01:01 Re: Converting pqsignal to void return