| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(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-04 03:20:27 |
| Message-ID: | 200707040320.l643KRh09981@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The use case is any system that uses temp tables in an OLTP setting,
> which certainly isn't uncommon. The problem is that today (and as well
> with a global temp table that is still writing to the catalogs) is that
> every OLTP operation that creates or drops a temp table is doing DDL.
> At best, that leads to a lot of catalog bloat. Right now, it appears to
> also expose some race conditions (we've got a customer that's been bit
> by this and we've been able to reproduce some odd behavior in the lab).
The solution is to fix the bloat, not add a work-around.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2007-07-04 07:22:11 | Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL |
| Previous Message | Kris Jurka | 2007-07-04 03:14:27 | Re: Why so many out-of-disk-space failures on buildfarm machines? |