From: A.M. <agentm@themactionfaction.com>
To: pgsql-performance@postgresql.org
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
Date: Tue, 3 Apr 2007 15:16:07 -0400
Message-ID: <EE4A4157-6E35-4DEC-B257-D08F1102F224@themactionfaction.com> (raw)
In-Reply-To: <4612A57B.2030601@agliodbs.com>
References: <4612A421.4060808@andromeiberica.com>
<4612A57B.2030601@agliodbs.com>
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.)
-M
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: agentm@themactionfaction.com
Subject: Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
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>
* 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