From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Terrence Brannon <metaperl(at)mac(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: temp tables versus the global sql area |
Date: | 2001-12-17 05:37:52 |
Message-ID: | 200112170537.fBH5bqS06826@candle.pha.pa.us |
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?
Nope. Sorry. Those caches would have to be invalidated if someone made
a change to those tables.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Terrence Brannon | 2001-12-17 10:41:09 | Re: Numbering Rows (SEQUENCE, OID) questions |
Previous Message | Tom Lane | 2001-12-17 01:33:30 | Re: why doesn't \d table_name show the table inheritance graph? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-12-17 05:39:27 | Re: performance tuning in large function / transaction |
Previous Message | Christopher Kings-Lynne | 2001-12-17 04:06:14 | Re: performance tuning in large function / transaction |