From: | Michael A Nachbaur <mike(at)nachbaur(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Temporary table performance? |
Date: | 2003-06-26 16:14:41 |
Message-ID: | 200306260914.41245.mike@nachbaur.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)nachbaur(dot)com>
* http://nachbaur.com/pgpkey.asc
*/
...[Arthur] leapt to his feet like an author hearing the phone ring...
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2003-06-26 17:23:39 | Re: Temporary table performance? |
Previous Message | Randall Lucas | 2003-06-26 16:05:17 | Re: Change the behaviour of the SERIAL "Type" |