From: Terrence Brannon <metaperl@mac.com>
To: pgsql-sql@postgresql.org
Subject: temp tables versus the global sql area
Date: Sun, 16 Dec 2001 15:54:16 -0800
Message-ID: <36AF7A62-F280-11D5-92F7-003065C2A10C@mac.com> (raw)
In-Reply-To: <20011211163822.O70071-100000@teak.adhesivemedia.com>
In the Momjian book it is stated:
Temporary tables are ideal for holding intermediate data used by
the current SQL session. For example, suppose you need to do many
SELECTs on the result of a complex query. An efficient strategy
is to execute the complex query once, then store the result in a
temporary table.
...However, my question is doesn't postgresql calculate the cost
of complex queries and store there result in some sort of global
sql area sorted by LRU or cost so that you can simply write
complex queries and take care of automatic caching?
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: metaperl@mac.com
Subject: Re: temp tables versus the global sql area
In-Reply-To: <36AF7A62-F280-11D5-92F7-003065C2A10C@mac.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