|From:||Robert Haas <robertmhaas(at)gmail(dot)com>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Bruce Momjian <bruce(at)momjian(dot)us>, Kris Jurka <books(at)ejurka(dot)com>, pgsql-performance(at)postgresql(dot)org|
|Subject:||Re: No hash join across partitioned tables?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Tue, Mar 2, 2010 at 12:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Feb 25, 2010 at 7:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Partially. There are stats now but autovacuum is not bright about
>>> when to update them.
>> Is that something you're planning to fix for 9.0? If not, we at least
>> need to document what we intend for people to do about it.
> I want to look at it, but I'm not sure whether the fix will be small
> enough that we want to put it in during beta.
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.
The Enterprise Postgres Company
|Next Message||Tom Lane||2010-06-09 20:11:25||Re: No hash join across partitioned tables?|
|Previous Message||Pierre C||2010-06-09 11:35:42||Re: Large (almost 50%!) performance drop after upgrading to 8.4.4?|
|Next Message||Tom Lane||2010-06-09 19:50:47||Re: Invalid YAML output from EXPLAIN|
|Previous Message||Dean Rasheed||2010-06-09 19:38:10||Re: Invalid YAML output from EXPLAIN|