Re: memcached and PostgreSQL

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: Michael Adler <adler(at)pobox(dot)com>, Darcy Buskermolen <darcy(at)wavefire(dot)com>
Subject: Re: memcached and PostgreSQL
Date: 2004-11-17 21:07:06
Message-ID: 200411171307.06584.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Michael,

> Still, it seems like a convenient way to maintain cache coherency,
> assuming that your application doesn't already have a clean way to do
> that.

Precisely. The big problem with memory caching is the cache getting out of
sync with the database. Updating the cache through database triggers helps
ameliorate that.

However, our inability to pass messages with NOTIFY somewhat limits the the
utility of this solution Sean wants "on commit triggers", but there's some
major issues to work out with that. Passing messages with NOTIFY would be
easier and almost as good.

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message David Parker 2004-11-17 21:31:31 sort_mem affect on inserts?
Previous Message Joshua D. Drake 2004-11-17 21:02:59 Re: Analyzer is clueless