[Pgpool-hackers] cache for pgpool

David Boreham david_list at boreham.org
Tue May 16 14:47:23 UTC 2006


>no need to change your application.
>just run pgpool and the requests are cached. If an update occurs, all
>the data caches for this table are cleared.
>just à la mysql. For my web application, mysql cache 67% of the
>requests and it is mandatory to have a cache if I want to switch to
>Postgres :-)
>  
>
You are aware that postgresql already has a cache, I presume ?
Typically the reason to reach for a second external cache is where the 
primary
database can't serve the total load : external caching is a form of 
replication
in that case. I'd recommend that you evaluate the performance of PG
for your application before concluding that it isn't going to provide
sufficient performance (it might, it might not, but you should really
find out before fixing on one plan).







More information about the Pgpool-hackers mailing list