I'm not sure about query result caching or 'relation caching', since the
first would seem to run into problems with concurrent updates, and the
second is sort-of what the buffer cache does.
Query plan caching sounds like a really good idea though. Neil Conway's
PREPARE patch already does this for an individual backend. Do you think
it would be hard to make it use shared memory, and check if a query has
already been prepared by another backend? Maybe it could use something
like a whitespace insensitive checksum for a shared hash key.
Regards,
John Nield
On Sun, 2002-08-25 at 20:15, Bruce Momjian wrote:
>
> Do we want to add "query caching" to the TODO list, perhaps with a
> question mark?
>
> ---------------------------------------------------------------------------
>
> Greg Sabino Mullane wrote:
[snip]
>
--
J. R. Nield
[EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
