pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Arnaud Lesauvage <arnaud.listes@codata.eu>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Cannot terminate backend
Date: Fri, 31 Mar 2023 15:55:35 +0200
Message-ID: <4fa776a4762bbdf774fb68d51a79cc0f5ca89aff.camel@cybertec.at> (raw)
In-Reply-To: <MRZP264MB2889C8F4000BE1B7EE85164A808F9@MRZP264MB2889.FRAP264.PROD.OUTLOOK.COM>
References: <MRZP264MB2889C8F4000BE1B7EE85164A808F9@MRZP264MB2889.FRAP264.PROD.OUTLOOK.COM>

On Fri, 2023-03-31 at 13:46 +0000, Arnaud Lesauvage wrote:
> I have a long running query that I seem unable to either cancel or terminate.
> What could be the reason for this, and what is the bet way to terminate this kind of query ?
>  
> The query is a CTE using postgis ST_ClusterDBSCAN function. The CTE returns approximately 150k rows.
> The SQL is as follows : 
> 
> EXPLAIN ANALYZE
> WITH subq AS (
>         SELECT id, geom, ST_ClusterDBSCAN(geom, eps := 1000, minpoints := 1) OVER() AS cluster_id
>         FROM mytable
> )
> SELECT cluster_id, count(id), ST_Collect(geom) 
> FROM subq
> GROUP BY cluster_id;
>  
> pg_stat_activity show no wait event.
> pg_cancel_backend(mypid) returns true but the state does not change in pg_stat_activity.
> pg_terminate_backend(mypid) yields the same result (as superuser)
> Pg_stat_activity show no wait_event.
>  
> SELECT version();
> PostgreSQL 14.5 (Ubuntu 14.5-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit

The most likely explanation is that one of the PostGIS functions runs for
a long time without checking CHECK_FOR_INTERRUPTS().
That would be a PostGIS bug.  Try to construct a reproducible test case
that you can share!

Perhaps this trick can help:
https://www.cybertec-postgresql.com/en/cancel-hanging-postgresql-query/

Yours,
Laurenz Albe





view thread (5+ messages)  latest in thread

Message-ID: <4fa776a4762bbdf774fb68d51a79cc0f5ca89aff.camel@cybertec.at>
Permalink:  ../4fa776a4762bbdf774fb68d51a79cc0f5ca89aff.camel@cybertec.at/
Also on:    postgresql.org/message-id/4fa776a4762bbdf774fb68d51a79cc0f5ca89aff.camel@cybertec.at

 · 

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-general@postgresql.org
  Cc: laurenz.albe@cybertec.at, arnaud.listes@codata.eu
  Subject: Re: Cannot terminate backend
  In-Reply-To: <4fa776a4762bbdf774fb68d51a79cc0f5ca89aff.camel@cybertec.at>
  References: <MRZP264MB2889C8F4000BE1B7EE85164A808F9@MRZP264MB2889.FRAP264.PROD.OUTLOOK.COM> <4fa776a4762bbdf774fb68d51a79cc0f5ca89aff.camel@cybertec.at>

* 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