Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > In going back through emails I had marked as possibly needing another
> > look before 9.0 is released, I came across this issue again. As I
> > understand it, analyze (or analyse) now collects statistics for both
> > the parent individually, and for the parent and its children together.
> > However, as I further understand it, autovacuum won't actually fire
> > off an analyze unless there's enough activity on the parent table
> > considered individually to warrant it. So if you have an empty parent
> > and a bunch of children with data in it, your stats will still stink,
> > unless you analyze by hand.
> > Assuming my understanding of the problem is correct, we could:
> > (a) fix it,
> > (b) document that you should consider periodic manual analyze commands
> > in this situation, or
> > (c) do nothing.
> > Thoughts?
> The objections to (a) are that it might result in excessive ANALYZE work
> if not done intelligently, and that we haven't got a patch ready anyway.
> I would have liked to get to this for 9.0 but I feel it's a bit late
What do we want to do about the above issue?
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ None of us is going to be here forever. +
In response to
pgsql-performance by date
|Next:||From: Craig Ringer||Date: 2010-07-02 03:00:51|
|Subject: Re: how to (temporarily) disable/minimize benefits of disk
block cache or postgresql shared buffer|
|Previous:||From: Eliot Gable||Date: 2010-07-02 00:46:13|
|Subject: Highly Efficient Custom Sorting|
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2010-07-02 03:14:17|
|Subject: Re: failover vs. read only queries|
|Previous:||From: Bruce Momjian||Date: 2010-07-02 02:44:48|
|Subject: Re: 9.0beta2 - server crash when using HS + SR|