From: Rod Taylor <pg@rbt.ca>
To: matt@ymogen.net
Cc: Aaron Werman <awerman2@hotmail.com>
Cc: Scott Kirkwood <scottakirkwood@gmail.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Caching of Queries
Date: Mon, 27 Sep 2004 13:37:51 -0400
Message-ID: <1096306670.40463.173.camel@jester> (raw)
In-Reply-To: <00e801c4a4b6$5526dd30$8300a8c0@solent>
References: <00e801c4a4b6$5526dd30$8300a8c0@solent>
> So yeah, here's another vote for this feature. It doesn't even need to
> happen automagically to be honest, so long as it's really simple for the
> client to turn on (preferably per-statement or per-table).
It might be easiest to shove the caching logic into pgpool instead.
Create an extension of EXPLAIN which returns data in an easy to
understand format for computers so that pgpool can retrieve information
such as a list of tables involved,
Extend LISTEN to be able to listen for a SELECT on a table --
replacement for dynamically adding triggers to send a notify on inserts,
updates, deletes.
Create some kind of generic LISTEN for structural changes. I know SLONY
could make use of triggers on ALTER TABLE, and friends as well.
When pg_pool is told to cache a query, it can get a table list and
monitor for changes. When it gets changes, simply dumps the cache.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pg@rbt.ca, matt@ymogen.net, awerman2@hotmail.com, scottakirkwood@gmail.com
Subject: Re: Caching of Queries
In-Reply-To: <1096306670.40463.173.camel@jester>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox