From: Michael A Nachbaur <mike@nachbaur.com>
To: pgsql-sql@postgresql.org
Subject: Temporary table performance?
Date: Thu, 26 Jun 2003 09:14:41 -0700
Message-ID: <200306260914.41245.mike@nachbaur.com> (raw)
Hello everyone,
In the Intranet application I've been building over the past 9 months, I have
developed quite a beast of a search. I've asked for help here in the past on
performance tuning it, and have come to the conclusion that I've gotten it as
tweaked as I can without seeking the counsel of a shamen.
What I'm looking at doing is improving in-page performance. In a nutshell, how
expensive is it to create a temporary table? I'd like to do something like:
CREATE TEMP TABLE SearchResults AS [......];
I could then do some queries against the temporary table without having to
regenerate the results every time I want to show a "Page 299 of 500" toolbar.
Would I be better off just sucking this data into an in-memory data structure,
or can I use a temp table as an easy-to-use alternative?
--
/* Michael A. Nachbaur <mike@nachbaur.com>
* http://nachbaur.com/pgpkey.asc
*/
...[Arthur] leapt to his feet like an author hearing the phone ring...
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-sql@postgresql.org
Cc: mike@nachbaur.com
Subject: Re: Temporary table performance?
In-Reply-To: <200306260914.41245.mike@nachbaur.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