Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: shawncarter(at)onboardeng(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
Date: 2024-12-05 20:13:45
Message-ID: bsm35hyfla5rylfbrrpml7dfaxaqj36je7z2h3h5vwf3emk72r@n6f7pkaen3uo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2024-12-05 13:07:03 -0500, Tom Lane wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2024-12-05 20:21:07 Re: [Bug] Heap Use After Free in Window Aggregate Execution
Previous Message Tom Lane 2024-12-05 18:50:49 Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows