Postgres Pro
Downloads
Home   >   mailing lists

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

From A.M.
Subject Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date
Msg-id C2FF82E3-27B4-41E3-8261-3DD4B42B9DC6@themactionfaction.com
Whole thread Raw
In response to Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"  (Alan Hodgson <ahodgson@simkin.ca>)
List pgsql-performance
Tree view 
On Apr 3, 2007, at 16:00 , Alan Hodgson wrote:

> 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?

The only difference between temporary tables and standard tables is
the WAL. Global temporary tables would be accessible by all sessions
and would be truncated on postmaster start. For a further potential
speed boost, global temp tables could be put in a ramdisk tablespace.

Well, that's at least how I envision them.

Cheers,
M

pgsql-performance by date:

Previous
From: Alan Hodgson
Date:
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Next
From: "Merlin Moncure"
Date:
Subject: Re: postgres 7.4 vs 8.x redux: query plans