From: | Matthias Howell <Matthias(dot)Howell(at)semeon(dot)com> |
---|---|
To: | Matthias Howell <Matthias(dot)Howell(at)semeon(dot)com>, "mtlpug(at)postgresql(dot)org" <mtlpug(at)postgresql(dot)org> |
Subject: | Re: vacuum question |
Date: | 2013-10-29 16:36:27 |
Message-ID: | D59001D0F7E96C46A119B694B7F2755AB5823B@MTL-IT-EXCH02.submtl.voxco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | mtlpug |
Running on postgres 9.1.1 on Red Hat eL 6
From: mtlpug-owner(at)postgresql(dot)org [mailto:mtlpug-owner(at)postgresql(dot)org] On Behalf Of Matthias Howell
Sent: Tuesday, October 29, 2013 11:14 AM
To: mtlpug(at)postgresql(dot)org
Subject: [mtlpug] vacuum question
my database stopped on Friday to prevent wrap around. I started a vacuum.
The vacuum is still running. it has been running on one table since Friday night at about 11 pm EDT. We have hit the 84 hour mark and have no idea how much longer it will run.
This is what I think I know:
The reason that I know the time is that the vacuum was waiting for an autovacuum that I killed and the autovacuum has been waiting since then.
The reason that I believe it to still be running is that it is a) not waiting in pg_stat_activity and b) when I run top I can see cpu and memory usage fluctuate for the vacuum process.
This from pgadmin:
The table has Rows (estimated) 1,270,070,000
and is 349 GB with Index size of 454 GB.
Dead tuples 280,968,228
Any ideas if we can estimate how much longer?
any help appreciated.
M
From | Date | Subject | |
---|---|---|---|
Next Message | Wolf Schwurack | 2016-12-22 20:37:02 | Target server's authentication method must be changed |
Previous Message | Matthias Howell | 2013-10-29 15:14:12 | vacuum question |