Re: query cache

Joshua Berkus <josh@agliodbs.com> writes:
> If you want to do something radical and new, then come up with a way
> for a client to request and then reuse a complete query plan by
> passing it to the server.

[ raised eyebrow ]  That seems like a complete nonstarter on two
different grounds: cache invalidation needs (client won't know if plan
is stale) and security issues (pass broken plan to server, crash
server).  Those problems could be avoided if the client simply has a
token for a plan that's kept on the server side ... but how is that
concept different from a prepared statement?
        regards, tom lane