Re: No hash join across partitioned tables?
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Bruce Momjian <bruce@momjian.us>, Kris Jurka <books@ejurka.com>, pgsql-performance <pgsql-performance@postgresql.org>
Date: 2010-10-26T12:23:26Z
Lists: pgsql-hackers, pgsql-performance
On Sat, Oct 16, 2010 at 1:22 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Alvaro Herrera <alvherre@commandprompt.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. Can we execute a SQL query at the point where we need this information? Because it doesn't seem too hard to work up a query that totals the inserts, updates, and reltuples across all children of each table. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company