From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Michael Adler <adler@pobox.com>
Cc: Darcy Buskermolen <darcy@wavefire.com>
Subject: Re: memcached and PostgreSQL
Date: Wed, 17 Nov 2004 13:07:06 -0800
Message-ID: <200411171307.06584.josh@agliodbs.com> (raw)
In-Reply-To: <20041117195158.GA18831@pobox.com>
References: <20041117040024.GB8838@pobox.com>
<200411170913.09390.darcy@wavefire.com>
<20041117195158.GA18831@pobox.com>
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
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: josh@agliodbs.com, adler@pobox.com, darcy@wavefire.com
Subject: Re: memcached and PostgreSQL
In-Reply-To: <200411171307.06584.josh@agliodbs.com>
* 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