From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Samuel Williams <space(dot)ship(dot)traveller(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Large data and slow queries |
Date: | 2017-04-19 13:25:10 |
Message-ID: | 20170419132510.GM9812@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
* Samuel Williams (space(dot)ship(dot)traveller(at)gmail(dot)com) wrote:
> Thanks for all the suggestions Stephen.
>
> > That explain analyze shows a whole ton of heap fetches. When was the
> last time a VACUUM was run on this table, to build the visibility map?
> Without the visibility map being current, an Index-Only Scan, as is
> happening here, can really suck.
>
> I'm using the default 9.6 config, I thought that auto-vacuum was on by default?
Sure, but that doesn't mean the table gets vacuumed. In particular,
actual vacuums are only kicked off when the number of *updated* or
*deleted* tuples passes the autovacuum threshold. If no updates or
deletes are done on the table (iow, it's essentially an insert-only or
insert-mostly table), the autovacuum daemon nevers runs a vacuum on it
(though it'll run analyze's).
Check pg_stat_all_tables to see when/if the table has actually been
vacuumed.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-04-19 13:39:42 | Re: Unable to upload backups |
Previous Message | Samuel Williams | 2017-04-19 13:13:11 | Re: Large data and slow queries |