Dimitri wrote:
> Now, as you see from your explanation, the Part #2 is the most
> dominant - so why instead to blame this query not to implement a QUERY
> PLANNER CACHE??? - in way if any *similar* query is recognized by
> parser we simply *reuse* the same plan?..
At least in JDBC, there's several open source prepared statement cache
implementations out there that people use. I don't know about other
client libraries, but it certainly is possible to do in the client.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com