Skip site navigation (1) Skip section navigation (2)

Re: memcached and PostgreSQL

From: Patrick B Kelly <pbk(at)patrickbkelly(dot)org>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: Michael Adler <adler(at)pobox(dot)com>,Darcy Buskermolen <darcy(at)wavefire(dot)com>, josh(at)agliodbs(dot)com,pgsql-performance(at)postgresql(dot)org,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: memcached and PostgreSQL
Date: 2004-11-22 07:59:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Nov 21, 2004, at 11:55 PM, Sean Chittenden wrote:

>> This is similar to sending email in a trigger or on commit where you 
>> can't be certain you send email always
>> and only on a commit.
> While this is certainly a possibility, it's definitely closer to the 
> exception and not the normal instance.

While an exception, this is a very real possibility in day to day 
operations. The absence of any feedback or balancing mechanism between 
the database and cache makes it impossible to know that they are in 
sync and even a small error percentage multiplied over time will lead 
to an ever increasing likelihood of error.

More dangerous is that this discrepancy will NOT always be apparent 
because without active verification of the correctness of the cache, we 
will not know about any errors unless the error grows to an obvious 
point. The errors may cause material damage long before they become 
obvious. This is a common failure pattern with caches.

Patrick B. Kelly

In response to


pgsql-performance by date

Next:From: Pierre-Frédéric CaillaudDate: 2004-11-22 12:30:04
Subject: Re: memcached and PostgreSQL
Previous:From: Constantin TeodorescuDate: 2004-11-22 07:44:04
Subject: Big number of schemas (3500) into a single database

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group