On Tue, Aug 01, 2017 at 03:36:23PM -0400, Peter Eisentraut wrote: > On 7/21/17 13:14, Jim Mlodgenski wrote: > > When I first saw this thread, my initial thought of a use case is to > > prepare some key application queries so they are there and ready to go. > > That would need to be before the ExecutorStart_hook or > > ProcessUtility_hook if an app would just want to execute the prepared > > statement. > > Isn't that what the preprepare extension does already?
more generic facility -> more useful
My use case is to pre-create TEMP schema elements that VIEWs, FUNCTIONs, and TRIGGERs, might need.
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)
So often creating local temp tables is antipattern (in Postgres) unfortunately.
I am not sure, if we should to support this case more :( Probably is better, so it is hard to use local TEMP tables.
