Re: [HACKERS] Management of simple_eval_estate for plpgsql DO blocks

2015-08-16 Thread Simon Riggs
On 14 August 2015 at 17:42, Tom Lane wrote: > The simplest fix for this would be to give up on the idea that DO blocks > use private simple_eval_estates, and make them use the shared one. > However, that would result in intra-transaction memory bloat for > transactions executing large numbers of

Re: [HACKERS] Management of simple_eval_estate for plpgsql DO blocks

2015-08-14 Thread Andrew Dunstan
On 08/14/2015 12:42 PM, Tom Lane wrote: In commit 0fc94a5ba I wrote: +* ... It's okay to update the [ session-wide ] +* hash table with the new tree because all plpgsql functions within a +* given transaction share the same simple_eval_estate. Um. Well, that's true for actual fun

[HACKERS] Management of simple_eval_estate for plpgsql DO blocks

2015-08-14 Thread Tom Lane
In commit 0fc94a5ba I wrote: +* ... It's okay to update the [ session-wide ] +* hash table with the new tree because all plpgsql functions within a +* given transaction share the same simple_eval_estate. Um. Well, that's true for actual functions, but plpgsql DO blocks use their own