Horton
Menu

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

Fujii Masao <masao.fujii@gmail.com>

View thread
From: Fujii Masao <masao.fujii@gmail.com>
To: Kirill Reshke <reshkekirill@gmail.com>
Cc: o15611@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2026-05-12T23:40:49Z
Lists: pgsql-bugs 
On Tue, May 12, 2026 at 10:59 PM Kirill Reshke <reshkekirill@gmail.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Make dblink interruptible, via new libpqsrv APIs.