Search Postgresql Archives

Re: Temp table or normal table for performance?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 19, 2009 at 08:10:14PM -0400, Stephen Cook wrote:
> I've decided on some type of table storage because basically I'm 
> combining information from several different tables (some of which need 
> to recursively get other rows) and massaging it and sorting it in ways 
> far too convoluted to use a single query with UNION and ORDER BY, and 
> then returning the results.

Sounds like you want a temp table to keep things in; you can add an ON
COMMIT DROP which should help keep things tidy.  If you're on 8.4 the
WITH clause may make this use case easier.

-- 
  Sam  http://samason.me.uk/

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux