Postgres Pro
Downloads
Home   >   mailing lists

Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000" - Mailing list pgsql-performance

From Alan Hodgson
Subject Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date
Msg-id 200704031300.46013@hal.medialogik.com
Whole thread Raw
In response to Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"  ("A.M." <agentm@themactionfaction.com>)
Responses Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
List pgsql-performance
Tree view 
On Tuesday 03 April 2007 12:47, "A.M." <agentm@themactionfaction.com> wrote:
> On Apr 3, 2007, at 15:39 , C. Bergström wrote:
> I would like to use transactional semantics over tables that can
> disappear whenever the server fails. memcached does not offer that.

How would temporary tables?

--
Ginsberg's Theorem:
 1) You can't win.
 2) You can't break even.
 3) You can't quit the game.

pgsql-performance by date:

Previous
From: "A.M."
Date:
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Next
From: "A.M."
Date:
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"