| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Vlad Bailescu <vlad(at)mojitosoftware(dot)com> |
| Subject: | Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker) |
| Date: | 2013-02-05 08:23:02 |
| Message-ID: | 20130205082302.GB32520@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 5, 2013 at 01:41:05PM +0530, Pavan Deolasee wrote:
> On Fri, Feb 1, 2013 at 10:53 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> >
> > Are these TODO items?
> >
>
> BTW, there are couple of TODOs.
>
> 1. Analyze should be done based on the total row churn across the
> parent + children. Looking at the parent only, as we do now, can
> result in analyzing too often or too seldom.
>
> 2. Auto-analyze should analyze parent and each child table in a
> separate transaction.
I added a link to this thread on the TODO list under:
Improve autovacuum tuning
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-02-05 08:26:41 | Re: json api WIP patch |
| Previous Message | Pavan Deolasee | 2013-02-05 08:11:05 | Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker) |