On Fri, Oct 6, 2017 at 3:36 PM, Nico Williams <n...@cryptonector.com> wrote: >> If global temporary tables should be effective, then you have not have >> modify system catalogue after creating. But lot of processes requires it - >> ANALYZE, query planning. > > But the nice thing about them is that you need only create them once, so > leave them in the catalog. Stats about them should not be gathered nor > stored, since they could be different per-session.
The topic of this thread seems to have drifted quite far from the subject line, but here are some links to previous discussions of global temporary tables. https://www.postgresql.org/message-id/flat/u2o603c8f071004231952i36642ae6u9d6a7eae6eb6ff32%40mail.gmail.com https://www.postgresql.org/message-id/AANLkTim=5af41BKFvZ=ofvj465kxqkjdjhqzudz3k...@mail.gmail.com https://www.postgresql.org/message-id/flat/CAFj8pRC2h6qhHsFbcE7b_7SagiS6o%3D5J2UvCwCb05Ka1XFv_Ng%40mail.gmail.com https://www.postgresql.org/message-id/flat/CA%2B0EDdACCx8w4nK-wdj-eodbJn4juChnHoUWVMM3u3uhLVPnJw%40mail.gmail.com I would strongly recommend reading through those carefully before undertaking anything here. This is not a straightforward project... -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
