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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: shawncarter(at)onboardeng(dot)com
Cc: 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 18:07:03
Message-ID: 2567618.1733422023@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

I guessed that the problem might be "the termination isn't effective
while the session is blocked on a lock", but in an experiment here
that worked for me. So I have no idea what was happening in
your case.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

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