From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | tony(at)exquisiteimages(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Analyze command running for 2063 minutes so far |
Date: | 2019-06-28 14:15:02 |
Message-ID: | 12082.1561731302@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
tony(at)exquisiteimages(dot)com writes:
> I started an Analyze command on a database Wednesday evening at around
> 9:00PM. it is now Friday morning at 8:00 and it is still running.
> ...
> I did try to execute:
> SELECT pg_cancel_backend(4029);
> and
> SELECT pg_terminate_backend(4029);
> but neither had any effect.
Hm, that's interesting. Can you get a stack trace from that process?
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
> I am running PostgreSQL version 9.3 on Ubuntu 14.04 with 128GB of
> memory, 800GB PCIe SSD for Database files, 1TB SATA SSD for WAL, 512GB
> SATA SSD for system files.
9.3.what exactly?
(You do know that 9.3.x is out of support, so even if this investigation
reveals a bug, we're not going to fix it in 9.3.x. I'm willing to look
anyway on the chance that there's a bug that also affects later versions.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | tony | 2019-06-28 15:06:03 | Re: Analyze command running for 2063 minutes so far |
Previous Message | Prakash Ramakrishnan | 2019-06-28 12:25:21 | Re: patch 11.2 to 11.4 |