Message-ID: <4C1BDD40.9030806@agliodbs.com>
Date: Fri, 18 Jun 2010 13:55:28 -0700
From: Josh Berkus <josh@agliodbs.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To: Pierre C <lists@peufeu.com>
CC: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL as a local in-memory cache
References: <cb0fb58c-9134-4314-a1d0-08fc39f911a6@40g2000pry.googlegroups.com>
	<18287446-8677-46d6-a581-c4777f60ebda@40g2000pry.googlegroups.com>
	<4C1A5B81.8050908@agliodbs.com> <m2typ18ow0.fsf@hi-media.com>
	<op.vegnqzoxeorkce@apollo13>
	<alpine.DEB.2.00.1006181002360.2534@aragorn.flymine.org>
	<op.veho55mieorkce@apollo13>
In-Reply-To: <op.veho55mieorkce@apollo13>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


> It must be a setting, not a version.
> 
> For instance suppose you have a session table for your website and a
> users table.
> 
> - Having ACID on the users table is of course a must ;
> - for the sessions table you can drop the "D"

You're trying to solve a different use-case than the one I am.

Your use-case will be solved by global temporary tables.  I suggest that
you give Robert Haas some help & feedback on that.

My use case is people using PostgreSQL as a cache, or relying entirely
on replication for durability.

-- 
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com