pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: mohankumar.dorairaj@globalfoundries.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16145: Not able to terminate active session
Date: Tue, 3 Dec 2019 15:11:47 +0100
Message-ID: <20191203141147.lofq3gwn3u3vkkze@development> (raw)
In-Reply-To: <16145-d617c77db801047b@postgresql.org>
References: <16145-d617c77db801047b@postgresql.org>

On Tue, Dec 03, 2019 at 01:18:50PM +0000, PG Bug reporting form wrote:
>The following bug has been logged on the website:
>
>Bug reference:      16145
>Logged by:          MOHAN KUMAR DORAIRAJ
>Email address:      mohankumar.dorairaj@globalfoundries.com
>PostgreSQL version: 11.2
>Operating system:   Red Hat Enterprise Linux Server release 7.6 (Maipo
>Description:
>
>Not able to terminate active session even though used below commands
>
>postgres=# SELECT pg_cancel_backend(16647);
> pg_cancel_backend
>-------------------
> t
>(1 row)
>
>postgres=# SELECT pg_terminate_backend(16647);
> pg_terminate_backend
>----------------------
> t
>(1 row)
>
>postgres=#  select pid,application_name FROM pg_stat_activity where
>application_name IS  NOT NULL AND state = 'active';
>  pid  |    application_name
>-------+------------------------
> 16647 | PostgreSQL JDBC Driver
> 19879 | psql
>

So what is happening in 16647? What query is it running? Can you attach
gdb to it and show us the backtrace?

It's probably running some CPU-intensive piece of code, not checking the
flags set by signal handlers, or something like that.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (15+ messages)  latest in thread

Message-ID: <20191203141147.lofq3gwn3u3vkkze@development>
Permalink:  ../20191203141147.lofq3gwn3u3vkkze@development/
Also on:    postgresql.org/message-id/20191203141147.lofq3gwn3u3vkkze@development

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tomas.vondra@2ndquadrant.com, mohankumar.dorairaj@globalfoundries.com
  Subject: Re: BUG #16145: Not able to terminate active session
  In-Reply-To: <20191203141147.lofq3gwn3u3vkkze@development>
  References: <16145-d617c77db801047b@postgresql.org> <20191203141147.lofq3gwn3u3vkkze@development>

* 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