Re: BUG #19473: regression error in dblink: another command is already in progress

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: o15611(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19473: regression error in dblink: another command is already in progress
Date: 2026-05-12 23:40:49
Message-ID: CAHGQGwHwA+214RimXya+4kdb7hguYrA_Zt4RicKVRe1Mwhfn4A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, May 12, 2026 at 10:59 PM Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>
> Doesn't dblink_is_busy violates this doc then? I mean, dblink_is_busy has side effect of changing connection state. Is this OK?

Maybe I'm missing your point...
Could you clarify what actual issue you are concerned about
with that use of dblink_is_busy()?

Regards,

--
Fujii Masao

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Xuneng Zhou 2026-05-13 00:46:25 Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending
Previous Message Alexander Lakhin 2026-05-12 20:00:00 Re: BUG #18158: Assert in pgstat_report_stat() fails when a backend shutting down with stats pending