temp tables versus the global sql area - Mailing list pgsql-sql

From Terrence Brannon
Subject temp tables versus the global sql area
Date
Msg-id 36AF7A62-F280-11D5-92F7-003065C2A10C@mac.com
Whole thread Raw
In response to Re: how does one replace a row in Postgresql? (ala MySQL REPLACE)  (Philip Hallstrom <philip@adhesivemedia.com>)
Responses Re: temp tables versus the global sql area
List pgsql-sql
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?



pgsql-sql by date:

Previous
From: Terrence Brannon
Date:
Subject: why doesn't \d table_name show the table inheritance graph?
Next
From: Tom Lane
Date:
Subject: Re: why doesn't \d table_name show the table inheritance graph?