> > > 2. Associate them with RelationOid, and we can record such information in > the > Append node as well. The bad part is the same relation Oid may appear > multiple > times in a query. for example: SELECT .. FROM p p1, p p2 where > p1.partkey1 = $1 > AND p2.partkey2 = $2; > > I just came up with a new idea. Since this situation should be rare, we can just come back to our original method (totally ignore the cost reduction) or use the average number. Fixing the 99% cases would be a big winner as well IMO.
So any hint on this will be appreciated.. > > -- > Best Regards > Andy Fan > -- Best Regards Andy Fan
