> 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 <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
