From: Michael Adler <adler@pobox.com>
To: Darcy Buskermolen <darcy@wavefire.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: memcached and PostgreSQL
Date: Wed, 17 Nov 2004 14:51:58 -0500
Message-ID: <20041117195158.GA18831@pobox.com> (raw)
In-Reply-To: <200411170913.09390.darcy@wavefire.com>
References: <20041117040024.GB8838@pobox.com>
<200411170913.09390.darcy@wavefire.com>
On Wed, Nov 17, 2004 at 09:13:09AM -0800, Darcy Buskermolen wrote:
> On November 16, 2004 08:00 pm, Michael Adler wrote:
> > http://pugs.postgresql.org/sfpug/archives/000021.html
> >
> > I noticed that some of you left coasters were talking about memcached
> > and pgsql. I'm curious to know what was discussed.
>
> Have a look at the pdf presentation found on the following site:
>
> http://people.freebsd.org/~seanc/pgmemcache/
Thanks for that.
That presentation was rather broad and the API seems rather general
purpose, but I wonder why you would really want access the cache by
way of the DB? If one major point of memcache is to allocate RAM to a
low-overhead server instead of to the RDBMS's disk cache, why would
you add the overhead of the RDBMS to the process? (this is a bit of
straw man, but just trying to flesh-out the pros and cons)
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.
(just my uninformed opinion, though...)
-Mike
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: adler@pobox.com, darcy@wavefire.com
Subject: Re: memcached and PostgreSQL
In-Reply-To: <20041117195158.GA18831@pobox.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