Re: Add missing CHECK_FOR_INTERRUPTS calls in dblink module - Mailing list pgsql-hackers

From Kirill Reshke
Subject Re: Add missing CHECK_FOR_INTERRUPTS calls in dblink module
Date
Msg-id CALdSSPhuCN_cS7MXobWx7Lh0adc-NWd8M115QMGC+yf21kCgNg@mail.gmail.com
Whole thread
In response to Add missing CHECK_FOR_INTERRUPTS calls in dblink module  (Lakshmi N <lakshmin.jhs@gmail.com>)
Responses Re: Add missing CHECK_FOR_INTERRUPTS calls in dblink module
List pgsql-hackers
On Tue, 10 Mar 2026 at 14:00, Lakshmi N <lakshmin.jhs@gmail.com> wrote:
>
> Hi All,
>
> This is my first patch submission, please guide me if I made any mistakes. I noticed that CHECK_FOR_INTERRUPTS is
missingat two places in dblink.c. Submitting a small patch to address this.
 
>
> Regards,
> Lakshmi
>
>

Hi!
Are you trying to fix any real problem? So, do you have any reproduces
where dblink stucks while processing tuples? I am somehow surprised if
we do not have CFI somewhere inside tuplestore_puttuple...


-- 
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: Xuneng Zhou
Date:
Subject: Re: Odd code around ginScanToDelete
Next
From: Pavel Borisov
Date:
Subject: Re: Odd code around ginScanToDelete