> From: Paul Ramsey
> Afraid so. You can wait longer, I guess. You may have found two bugs… the
> lack of an interrupt in the dbscan loop, which I’m working on now. And maybe
> an infinite looping case? In which case if you want a fix on that, you’ll
> have to share your data and query.
I le
Afraid so. You can wait longer, I guess. You may have found two bugs… the lack
of an interrupt in the dbscan loop, which I’m working on now. And maybe an
infinite looping case? In which case if you want a fix on that, you’ll have to
share your data and query.
P.
> On Mar 31, 2023, at 7:41 AM,
> On Fri, 2023-03-31 at 13:46 +, 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_ClusterDBSC
On Fri, 2023-03-31 at 13:46 +, 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 functi
Hi all,
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 f
