Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active" - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
Date
Msg-id bsm35hyfla5rylfbrrpml7dfaxaqj36je7z2h3h5vwf3emk72r@n6f7pkaen3uo
Whole thread Raw
In response to Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,

On 2024-12-05 13:07:03 -0500, Tom Lane wrote:
> PG Bug reporting form <noreply@postgresql.org> writes:
> > pg_terminate_backend failed to terminate active queries on a materialized
> > view until an "idle in transaction" backend tied to the same view was
> > terminated.
> 
> Can't do much with this report if you don't give a full recipe for
> reproducing it.

In case a reproducer is not easily achievable, a backtrace showing where in
the code the unresponsive backend is, might suffice to identify the problem.


Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
Next
From: Koichi Suzuki
Date:
Subject: Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows