| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <janwieck(at)yahoo(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, jack <datactrl(at)tpg(dot)com(dot)au>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: call the same pl/pgsql procedure twice in the same connection |
| Date: | 2002-03-26 00:35:07 |
| Message-ID: | 5158.1017102907@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Jan Wieck <janwieck(at)yahoo(dot)com> writes:
> This is somehow connected to the temporary view discussion,
> as it needs the same detection if a query depends on
> temporary objects. As soon as we have a detection mechanism
> for it, I can modify PL/pgSQL not to save prepared plans for
> these statements.
Actually, I don't think plpgsql should make any special discrimination
against temp tables; it should be able to re-use a query plan for
exactly as long as the temp table exists. But I agree that we need
a mechanism for tracking query-plan dependencies for this to happen.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleus Mantzios | 2002-03-26 08:12:12 | Arrays Design Question |
| Previous Message | chester c young | 2002-03-25 21:41:12 | Re: quickest query to check a table for existance of a value in a field |