Re: How to debug a connection that's "active" but hanging?

From: Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jurrie Overgoor <postgresql-mailinglist(at)jurr(dot)org>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: How to debug a connection that's "active" but hanging?
Date: 2021-07-12 18:56:15
Message-ID: CAM+6J96Leay_mMqvP6kg6sqrD2KZrWYOmGkThictEz2PK=HhcA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 12 Jul 2021 at 23:16, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>
> The backtraces you captured look like the query is not "hung", it's
> just computing away.
>
>
He mentioned earlier that the query was hung as 'active' for 8 hours and on.

incase this is due to bad plan,
@Jurrie Overgoor <postgresql-mailinglist(at)jurr(dot)org> is it also possible for
you to run manually

`vacuumdb -a -v` from the terminal, each time before you run your test
suite for some runs, do you still get the same issue?

I have a feeling repeated runs may have caused a lot of bloat on some
tables which might have not been reclaimed by autovacuum runs.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jurrie Overgoor 2021-07-12 20:56:53 Re: How to debug a connection that's "active" but hanging?
Previous Message Rich Shepard 2021-07-12 18:13:58 Re: Use of '&' as table prefix in query [RESOLVED]