pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
3+ messages / 3 participants
[nested] [flat]

* BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
@ 2024-12-04 23:55  PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 1 reply; 3+ messages in thread

From: PG Bug reporting form @ 2024-12-04 23:55 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: shawncarter@onboardeng.com

The following bug has been logged on the website:

Bug reference:      18734
Logged by:          Shawn C
Email address:      shawncarter@onboardeng.com
PostgreSQL version: 16.4
Operating system:   Amazon Linux AMI
Description:        

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.



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
@ 2024-12-05 18:07  Tom Lane <tgl@sss.pgh.pa.us>
  parent: PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2024-12-05 18:07 UTC (permalink / raw)
  To: shawncarter@onboardeng.com; +Cc: pgsql-bugs@lists.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





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active"
@ 2024-12-05 20:13  Andres Freund <andres@anarazel.de>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 3+ messages in thread

From: Andres Freund @ 2024-12-05 20:13 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: shawncarter@onboardeng.com; pgsql-bugs@lists.postgresql.org

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





^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2024-12-05 20:13 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-12-04 23:55 BUG #18734: pg_terminate_backend was unresponsive for processes with the status "active" PG Bug reporting form <noreply@postgresql.org>
2024-12-05 18:07 ` Tom Lane <tgl@sss.pgh.pa.us>
2024-12-05 20:13   ` Andres Freund <andres@anarazel.de>

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