Re: plan time of MASSIVE partitioning ...
Leonardo Francalanci <m_lists@yahoo.it>
From: Leonardo Francalanci <m_lists@yahoo.it>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Boszormenyi Zoltan <zb@cybertec.at>, pgsql-hackers Hackers <pgsql-hackers@postgresql.org>
Date: 2010-10-29T15:41:18Z
Lists: pgsql-hackers
> This is going to be dominated by constraint exclusion checking. There's
> basically no fix for that except a more explicit representation of the
> partitioning rules.
Damn, I knew that was going to be more complicated :)
So in which case does this patch help? I guess in a multi-index
scenario? childtables.sql is kind of hard to read (I think a FOR loop
would have been more auto-explaining?).