| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Creager <robertc(at)spectralogic(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query hitting empty tables taking 48 minutes |
| Date: | 2018-06-08 16:23:41 |
| Message-ID: | CAKFQuwbF8rxeB9L8T+wBkKiaujyDmHzuAQyyaV9aXFE9nGMAaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jun 8, 2018 at 9:17 AM, Robert Creager <robertc(at)spectralogic(dot)com>
wrote:
> A nightly VACUUM FULL which ran based on heuristics resolved the problem.
> This would seem to point to a db problem more than an app problem? I’m
> unsure how the app could have an affect of this magnitude on the database,
> although I’d love to be told otherwise.
>
Not sure what the right answer is but its seems your database (those
tables at least) are mis-configured for the workload being executed
against them. Significantly increasing the aggressiveness of the
auto-vacuum process and/or inserting manual vacuum analyze commands into
your application at appropriate times are probably necessary.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Creager | 2018-06-08 16:39:21 | Re: Query hitting empty tables taking 48 minutes |
| Previous Message | Robert Creager | 2018-06-08 16:17:47 | Re: Query hitting empty tables taking 48 minutes |