| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL |
| Date: | 2007-07-05 06:26:49 |
| Message-ID: | 87ejjnwel2.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>>> 2007/7/4, Bruce Momjian <bruce(at)momjian(dot)us>:
>> The solution is to fix the bloat, not add a work-around.
>
>> The bloat is a direct consequence of performing DDL in the midst of an OLTP
>> transaction.
>
> Hardly. It's a consequence of our current implementation of temp
> tables; that does not necessarily imply that we cannot fix it without
> an API change.
Sure, we could change our regular temporary tables to not create new records
in pg_class at all, but I don't think it would make a big difference to DSS
users. And I think for OLTP you would still want all the other advantages the
standard api gives you.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-07-05 06:34:14 | Re: what is difference between LOCAL and GLOBAL TEMPTABLES in PostgreSQL |
| Previous Message | Magnus Hagander | 2007-07-05 04:59:57 | Re: script binaries renaming |