Joshua Rubin wrote: > 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.
Then you would benefit from using prepared statements in the client, and/or connection pooling to avoid having to re-prepare because of reconnecting. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
