From: | Kaijiang Chen <chenkaijiang(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | weird long time query |
Date: | 2019-12-17 02:58:17 |
Message-ID: | CAAkGvS8ocfeVFOCsxoAY6suzMkrW+O9twRAQ2c4WrZNbQ=vSpg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general pgsql-performance |
I'm using postgres 9.4.17 on centos 7.
I check the running queries with the following SQL:
SELECT
procpid,
start,
now() - start AS lap,
current_query
FROM
(SELECT
backendid,
pg_stat_get_backend_pid(S.backendid) AS procpid,
pg_stat_get_backend_activity_start(S.backendid) AS start,
pg_stat_get_backend_activity(S.backendid) AS current_query
FROM
(SELECT pg_stat_get_backend_idset() AS backendid) AS S
) AS S
WHERE
current_query <> '<IDLE>'
ORDER BY
lap DESC;
Then, I found a SQL that has run for some days (and still running):
procpid | 32638
start | 2019-11-25 16:29:29.529318+08
lap | 21 days 18:24:54.707369
current_query | DEALLOCATE pdo_stmt_00000388
I tried to kill it with: SELECT pg_cancel_backend(32638) but it takes no
effects.
What's this query and what shall I do for it?
Best Wishes
Kaijiang
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Lakhin | 2019-12-17 03:00:00 | Re: BUG #16161: pg_ctl stop fails sometimes (on Windows) |
Previous Message | Tomas Vondra | 2019-12-16 21:02:49 | Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Zhidenkov | 2019-12-17 08:41:47 | Re: Race condition while creating a new partition |
Previous Message | Adrian Klaver | 2019-12-17 00:39:31 | Re: Experiencing error during restore - found unexpected block ID (0) |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-12-17 04:04:45 | Re: Consecutive Query Executions with Increasing Execution Time |
Previous Message | Sam Gendler | 2019-12-17 00:53:31 | Re: Consecutive Query Executions with Increasing Execution Time |