| From: | Terrence Brannon <metaperl(at)mac(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | temp tables versus the global sql area |
| Date: | 2001-12-16 23:54:16 |
| Message-ID: | 36AF7A62-F280-11D5-92F7-003065C2A10C@mac.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Terrence Brannon | 2001-12-17 00:00:53 | why doesn't \d table_name show the table inheritance graph? |
| Previous Message | Stephan Szabo | 2001-12-16 19:42:41 | Re: Numbering Rows (SEQUENCE, OID) questions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Terrence Brannon | 2001-12-17 00:00:53 | why doesn't \d table_name show the table inheritance graph? |
| Previous Message | Stephan Szabo | 2001-12-16 19:42:41 | Re: Numbering Rows (SEQUENCE, OID) questions |