From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Christopher Browne <cbbrowne@acm.org>
Subject: Re: Need help to decide Mysql vs Postgres
Date: Mon, 06 Jun 2005 12:02:27 -0700
Message-ID: <42A49DC3.1030800@cheapcomplexdevices.com> (raw)
In-Reply-To: <m34qcbbesc.fsf@knuth.cbbrowne.com>
References: <0C072E7CC947D511AC9600A0CC7341200256CF37@xeon400.tagaudit.com>
<m34qcbbesc.fsf@knuth.cbbrowne.com>
Christopher Browne wrote:
>
> There is a common "use case" where MySQL(tm) ...
>
> select * from some_table where id='some primary key value';
>
> If your usage patterns differ from that...
However this is a quite common use-case; and I wonder what the
best practices for postgresql is for applications like that.
I'm guessing the answer is PGMemcache?
(http://people.freebsd.org/~seanc/pgmemcache/pgmemcache.pdf)
... with triggers and listen/notify to manage deletes&updates
and tweaks to the application code to look to memcached for
those primary_key=constant queries?
If that is the answer, I'm curious if anyone's benchmarked
or even has qualitative "yeah, feels very fast" results for
such an application for the common mysql use case.
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: rm_pg@cheapcomplexdevices.com, cbbrowne@acm.org
Subject: Re: Need help to decide Mysql vs Postgres
In-Reply-To: <42A49DC3.1030800@cheapcomplexdevices.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