Rohit, > Now, when I do a select on the basetable with a range of ids, it looks up > each subtable that inherits from the base table and using an indexed scan > searches for values in the range. It does it even for subtables whose check > constraint completely rules out the possibility of it containing any such > row . Should not check constraint act as the first filter? The index should > ideally be scanned only when the check constraint is passed by the search > criteria but surprisingly it did not happen. The explain analyze showed > cost for index scans of subtables that cannot contain rows matching the > search criteria.
This is called "range partitioning". We're working on it. You're welcome to join the Bizgres project where most of the discussion on this feature takes place: www.bizgres.org http://pgfoundry.org/mail/?group_id=1000107 -- Josh Berkus Aglio Database Solutions San Francisco ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
