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

From Tom Lane
Subject Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
Date
Msg-id 2567618.1733422023@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18735: Specific multibyte character in psql file path command parameter for Windows
Next
From: Tom Lane
Date:
Subject: Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows