From: "C. Bergström" <cbergstrom@netsyncro.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date: Tue, 03 Apr 2007 22:39:51 +0300
Message-ID: <4612AD87.1040406@netsyncro.com> (raw)
In-Reply-To: <EE4A4157-6E35-4DEC-B257-D08F1102F224@themactionfaction.com>
References: <4612A421.4060808@andromeiberica.com>
<4612A57B.2030601@agliodbs.com>
<EE4A4157-6E35-4DEC-B257-D08F1102F224@themactionfaction.com>
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/
Implementing a cleaner more transparent sql wrapper would be even nicer.
http://tangent.org/index.pl?lastnode_id=478&node_id=506
Just sharing/tossing some ideas around..
C.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cbergstrom@netsyncro.com
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
In-Reply-To: <4612AD87.1040406@netsyncro.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox