pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matt Clark <matt@ymogen.net>
To: Rod Taylor <pg@rbt.ca>
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 21:30:31 +0100
Message-ID: <41587867.4090505@ymogen.net> (raw)
In-Reply-To: <1096306670.40463.173.camel@jester>
References: <00e801c4a4b6$5526dd30$8300a8c0@solent>
	<1096306670.40463.173.camel@jester>


>It might be easiest to shove the caching logic into pgpool instead.
>
>...
>
>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.
>
>
>  
>
It's certainly the case that the typical web app (which, along with 
warehouses, seems to be one half of the needy apps), could probably do 
worse than use pooling as well.  I'm not well up enough on pooling to 
know how bulletproof it is though, which is why I included it in my list 
of things that make me go 'hmm....'.  It would be really nice not to 
have to take both things together.

More to the point though, I think this is a feature that really really 
should be in the DB, because then it's trivial for people to use.  
Taking an existing production app and justifying a switch to an extra 
layer of pooling software is relatively hard compared with grabbing data 
from a view instead of a table (or setting a variable, or adding a tweak 
to a query, or however else it might be implemented).

Eminiently doable in pgpool though, and just the right thing for anyone 
already using it.

M



view thread (72+ messages)  latest in thread

Message-ID: <41587867.4090505@ymogen.net>
Permalink:  ../41587867.4090505@ymogen.net/
Also on:    postgresql.org/message-id/41587867.4090505@ymogen.net

 · 

reply

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: matt@ymogen.net, pg@rbt.ca, awerman2@hotmail.com, scottakirkwood@gmail.com
  Subject: Re: Caching of Queries
  In-Reply-To: <41587867.4090505@ymogen.net>

* 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