From: Michael Adler <adler@pobox.com>
To: pgsql-performance@postgresql.org
Subject: memcached and PostgreSQL
Date: Tue, 16 Nov 2004 23:00:24 -0500
Message-ID: <20041117040024.GB8838@pobox.com> (raw)
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.
In reading about memcached, it seems that many people are using it to
circumvent the scalability problems of MySQL (lack of MVCC).
from their site:
<snip>
Shouldn't the database do this?
Regardless of what database you use (MS-SQL, Oracle, Postgres,
MysQL-InnoDB, etc..), there's a lot of overhead in implementing ACID
properties in a RDBMS, especially when disks are involved, which means
queries are going to block. For databases that aren't ACID-compliant
(like MySQL-MyISAM), that overhead doesn't exist, but reading threads
block on the writing threads. memcached never blocks.
</snip>
So What does memcached offer pgsql users? It would still seem to offer
the benefit of a multi-machined cache.
-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
Subject: Re: memcached and PostgreSQL
In-Reply-To: <20041117040024.GB8838@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