Re: parser_analyze freeing memory which is later referenced

Kevin Grittner <kgrittn@ymail.com> writes:
> I'm using valgrind to find a problem with materialized views, and
> ran into this, which I have confirmed is present on the master
> branch as of 7803e9327db3788f68d820c19f4081afb79edd12.

> Memory freed here:
> ... is later referenced at these places:

[ squint... ]  Not sure I believe that, as building with
CLOBBER_FREED_MEMORY (ie, any assert-enabled build) really ought to
expose such problems pretty quickly.  What's your test case?
        regards, tom lane