Re: Curing plpgsql's memory leaks for statement-lifespan values

In
https://www.postgresql.org/message-id/tencent_5C738ECA65BAD6861AA43E8F@qq.com
it was pointed out that you could get an intra-function-call memory leak
from something like

        LOOP
          BEGIN
            EXECUTE 'bogus command';
          EXCEPTION WHEN OTHERS THEN
          END;
        END LOOP;

Another answer is to invent a third per-function memory context intended
to hold statement-lifespan variables.