Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"

From: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date: 2007-04-03 19:47:41
Message-ID: E03A51A8-4E4E-4975-A05F-AACB9791E326@themactionfaction.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On Apr 3, 2007, at 15:39 , C. Bergström wrote:

> A.M. wrote:
>> Indeed... I looked through the official TODO list and was unable
>> to find an entry for global temporary tables- such a thing would
>> be ideal for any transient data such as web sessions or
>> materialized views. Is there any reason why global temp tables
>> shouldn't be implemented? (And, no, I'm not simply referring to
>> "in-memory" tables- they can simply be handled with a ram disk.)
> Not exactly what you're looking for and a simple API, but the
> performance is very nice and has a lot of potential.
>
> http://pgfoundry.org/projects/pgmemcache/

I would like to use transactional semantics over tables that can
disappear whenever the server fails. memcached does not offer that.

Cheers,
M

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alan Hodgson 2007-04-03 20:00:45 Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Previous Message C. Bergström 2007-04-03 19:39:51 Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"