From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Kris Jurka <books(at)ejurka(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: No hash join across partitioned tables? |
Date: | 2010-10-16 05:22:42 |
Message-ID: | 29559.1287206562@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> If we analyze the parent, do we also update the children stats, or is it
> just that we keep two stats for the parent, one with children and one
> without, both being updated when the parent is analyzed?
The latter.
The trick here is that we need to fire an analyze on the parent even
though only its children may have had any updates.
> If the latter's the case, maybe we should modify ANALYZE a bit more, so
> that we can analyze the whole hierarchy in one go, and store the lot of
> stats with a single pass (each child alone, the parent alone, the parent
> plus children). However it's not real clear how would this work with
> multiple inheritance levels.
It's also not clear how it works without blowing out memory...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel Gendler | 2010-10-16 05:35:46 | Re: No hash join across partitioned tables? |
Previous Message | Alvaro Herrera | 2010-10-16 05:03:02 | Re: No hash join across partitioned tables? |
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel Gendler | 2010-10-16 05:35:46 | Re: No hash join across partitioned tables? |
Previous Message | Alvaro Herrera | 2010-10-16 05:03:02 | Re: No hash join across partitioned tables? |