Some comments about 0003 patch.
@@ -996,10 +996,20 @@ inheritance_planner(PlannerInfo *root)
Index rti;
+ RangeTblEntry *parent_rte;
There's already another variable declared in that function within a loop
foreach(lc, root->append_rel_list)
{
...
RangeTblEntry *parent_rte;
RangeTblEntry *child_rte;You might want to choose a different name or delete the one within the loop. I am wondering whether we should deal with inh flat reset in a slightly different way. Let expand_inherited_rtentry() mark inh = false for the partitioned tables without any partitions and deal with those at the time of estimating size by marking those as dummy. That might be better than multiple changes here. I will try to cook up a patch soon for that. Also we should add tests to make sure the scans on partitioned tables without any partitions do not get into problems. PFA patch which adds those tests. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
0003-Always-plan-partitioned-tables-as-inheritance-sets_v2.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
