From: Tom Lane <tgl@sss.pgh.pa.us>
To: shawncarter@onboardeng.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
Date: Thu, 05 Dec 2024 13:07:03 -0500
Message-ID: <2567618.1733422023@sss.pgh.pa.us> (raw)
In-Reply-To: <18734-3dfe0282d2e102c2@postgresql.org>
References: <18734-3dfe0282d2e102c2@postgresql.org>
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.
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, shawncarter@onboardeng.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
In-Reply-To: <2567618.1733422023@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox