Tom, > If you're depending on constraint exclusion, it's hard to see how plan > caching could help you at all. The generated plan needs to vary > depending on the actual WHERE-clause parameters. Thank you for the reply. We "hardcode" the parts of the where clause so that the prepared plan will not vary among the possible partitions of the table. The only values that are bound would not affect the planner's choice of table. Thanks, Joshua
Attachment:
signature.asc
Description: OpenPGP digital signature
