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

From Pavan Deolasee
Subject Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)
Date
Msg-id CABOikdPnqVe5v9ZZKROwNcLE3S6Jx-KS-mi8D5ovJxNaM6uVFg@mail.gmail.com
Whole thread Raw
In response to Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Fri, Feb 1, 2013 at 10:53 PM, Bruce Momjian <bruce@momjian.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



pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)
Next
From: Bruce Momjian
Date:
Subject: Re: Turning auto-analyze off (was Re: [GENERAL] Unusually high IO for autovacuum worker)