| From: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | John R Pierce <pierce(at)hogranch(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Reindex taking forever, and 99% CPU |
| Date: | 2014-08-03 02:37:08 |
| Message-ID: | CAFWfU=uZJh88k7sETVmMZ9eWRMhiB4aLOFRhvJgCEM8CW_260w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> In your original post you said it was stopping on pg_class so now I am
> confused.
No need to be confused. The vacuum thing is a bit tricky for laymen
like myself. The "pg_class" seemed to be associated to this table.
Anyway, even before the upgrade, the vacuum was stopping at this table
and taking forever.
The question is: what now. Where can I give you information from?
IOSTAT I've already shared.
Will the work_mem settings affect the manual REINDEX that's still
running? What can I do to speed up the REINDEX? Should I change my
autovacuum settings for this table specifcally (it's the only mammoth
table in the DB, and our main one)?
Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-08-03 04:08:45 | Re: Reindex taking forever, and 99% CPU |
| Previous Message | Adrian Klaver | 2014-08-03 02:26:06 | Re: Reindex taking forever, and 99% CPU |