Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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:11:05
Message-ID: CABOikdPnqVe5v9ZZKROwNcLE3S6Jx-KS-mi8D5ovJxNaM6uVFg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Thanks,
Pavan

--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-02-05 08:23:02 Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)
Previous Message Pavan Deolasee 2013-02-05 08:07:19 Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)