Re: Query meltdown: caching results

[Gregory Stark <stark(at)enterprisedb(dot)com>]

"Norman Peelman" <npeelman(at)cfl(dot)rr(dot)com> writes:

>> My options are, as far as I can tell,
>>
>> 1) replace the Database PDO extending class with something else that
>> provides query results caching in PHP, or
>> 2) get Postgres itself to cache the results of queries to avoid
>> running them repeatedly during a session.

You might consider looking at memcached. One way to use it would be to have
the PHP application check for the cached object first and use it rather than
do any database queries. Then you can use pgmemcached to allow triggers to
invalidate cached objects whenever the underlying data changes. (Or you could
even just use pl/php to update or invalidate the cached object through the
same code library)

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's Slony Replication support!