Re: pg_temp_%d namespace creation can invalidate all the cached plan in other backends

2021-02-23 Thread Andy Fan
On Tue, Feb 23, 2021 at 1:50 PM Tom Lane wrote: > Andy Fan writes: > > Planning is expensive and we use plancache to bypass its effect. I find > the > > $subject recently which is caused by we register NAMESPACEOID > invalidation > > message for pg_temp_%s as well as other normal namespaces. Is

Re: pg_temp_%d namespace creation can invalidate all the cached plan in other backends

2021-02-22 Thread Tom Lane
Andy Fan writes: > Planning is expensive and we use plancache to bypass its effect. I find the > $subject recently which is caused by we register NAMESPACEOID invalidation > message for pg_temp_%s as well as other normal namespaces. Is it a > must? Since we don't normally delete those namespaces

Re: pg_temp_%d namespace creation can invalidate all the cached plan in other backends

2021-02-22 Thread Andy Fan
On Tue, Feb 23, 2021 at 12:07 PM Andy Fan wrote: > Planning is expensive and we use plancache to bypass its effect. I find the > $subject recently which is caused by we register NAMESPACEOID invalidation > message for pg_temp_%s as well as other normal namespaces. Is it a > must? > > We can demo