| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Jaime Casanova" <systemguards(at)gmail(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jim Nasby" <decibel(at)decibel(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL |
| Date: | 2007-07-03 05:08:36 |
| Message-ID: | 162867790707022208w267d43aard8ee2dabc219bb38@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2007/7/3, Gregory Stark <stark(at)enterprisedb(dot)com>:
>
> "Jaime Casanova" <systemguards(at)gmail(dot)com> writes:
>
> > while not just a new rekind indicating this is a template and not and
> > actual table. and using that template for creating the actual tables?
>
> For precisely the reason stated upthread. That would mean creating and
> deleting catalog entries for every transaction. Imagine a busy OLTP system
> running hundreds of transactions per second trying to use a temporary table
> for intermediate results. Mixing DDL and DML is just as bad an idea behind the
> scenes as it is for users.
>
Global temp table can be created from template only when is used. It's
has not negative efect on app which doesn't use it. The benefit of
g.t.t. is simplifycation of stored procedures.
regards
Pavel Stehule
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2007-07-03 05:14:24 | Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL |
| Previous Message | Joshua D. Drake | 2007-07-03 04:18:34 | Re: Still recommending daily vacuum... |