Re: parser_analyze freeing memory which is later referenced

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: parser_analyze freeing memory which is later referenced
Date: 2013-02-12 00:47:01
Message-ID: 3151.1360630021@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner <kgrittn(at)ymail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2013-02-12 01:53:33 Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Previous Message Alvaro Herrera 2013-02-11 23:27:03 Re: palloc unification