Re: Tom Lane 2016-07-30 <1184.1469890...@sss.pgh.pa.us> > In short, I think that the way to make something like this work is to > figure out how to have "virtual" catalog rows describing a temp table. > Or maybe to partition the catalogs so that vacuuming away temp-table > rows is easier/cheaper than today.
We should also be thinking about how the opposite idea of "global" temp tables (I believe that's what Oracle calls them) would work. These have a persistent structure in the catalogs, just the data is private to every session (or transaction); every connection starts with an empty temp table and for their use. I'd guess that type of global temp tables would fix the bloat problem also very efficiently. (Ad-hoc temp tables shouldn't occur that often so the bloat caused by them wouldn't matter that much. If they do, their structure is likely always the same, and they could be made "global" in the schema.) The bit that needs to be thought out here would be how to maintain statistics for these tables. Obviously ANALYZE shouldn't update any globally visible data. Christoph -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
