On Fri, Oct 06, 2017 at 11:04:38AM +0800, Craig Ringer wrote: > On 6 October 2017 at 10:52, Pavel Stehule <pavel.steh...@gmail.com> wrote: > > > It is better to work on GLOBAL TEMP tables. > > > > Current TEMP tables, if you do it for any session has pretty significant > > overhead - with possible risk of performance lost (system catalog bloat). > > > > pretty significant performance issue of my customers are related to temp > > tables usage (under high load) > > I've seen the same thing too. Especially when combined with logical > decoding, where IIRC we mark transactions as having catalog changes > due to temp tables. > > Sometimes the catalog bloat can be truly horrible when a user has > hundreds of plpgsql functions that all like to make temp tables.
I agree that we should have GLOBAL TEMP tables, but also we should have a pg_temp_catalog where all TEMP schema elements go... (That, I'm sure, would be a lot of work.) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
