public inbox for [email protected]  

help / color / mirror / Atom feed

From: Kirill Reshke <[email protected]>
To: Lakshmi N <[email protected]>
Cc: [email protected]
Subject: Re: Add missing CHECK_FOR_INTERRUPTS calls in dblink module
Date: Tue, 10 Mar 2026 14:25:10 +0500
Message-ID: <CALdSSPhuCN_cS7MXobWx7Lh0adc-NWd8M115QMGC+yf21kCgNg@mail.gmail.com> (raw)
In-Reply-To: <CA+3i_M-fFb4cZ4SYToBft5VERvo0AZ22LRfzLE5axpGr9YsgPg@mail.gmail.com>
References: <CA+3i_M-fFb4cZ4SYToBft5VERvo0AZ22LRfzLE5axpGr9YsgPg@mail.gmail.com>

On Tue, 10 Mar 2026 at 14:00, Lakshmi N <[email protected]> wrote:
>
> Hi All,
>
> This is my first patch submission, please guide me if I made any mistakes. I noticed that CHECK_FOR_INTERRUPTS is missing at 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

view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Add missing CHECK_FOR_INTERRUPTS calls in dblink module
  In-Reply-To: <CALdSSPhuCN_cS7MXobWx7Lh0adc-NWd8M115QMGC+yf21kCgNg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox