Re: plan time of MASSIVE partitioning ...
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Boszormenyi Zoltan <zb@cybertec.at>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@commandprompt.com>, Stephen Frost <sfrost@snowman.net>, Hans-Jürgen Schönig <postgres@cybertec.at>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers Hackers <pgsql-hackers@postgresql.org>, Josh Berkus <josh@agliodbs.com>
Date: 2010-10-27T15:41:00Z
Lists: pgsql-hackers
On 26.10.2010 18:34, Boszormenyi Zoltan wrote: > thank you very much for pointing me to dynahash, here is the > next version that finally seems to work. > > Two patches are attached, the first is the absolute minimum for > making it work, this still has the Tree type for canon_pathkeys > and eq_classes got the same treatment as join_rel_list/join_rel_hash > has in the current sources: if the list grows larger than 32, a hash table > is created. It seems to be be enough for doing in for > get_eclass_for_sort_expr() > only, the other users of eq_classes aren't bothered by this change. That's better, but can't you use dynahash for canon_pathkeys as well? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com