Re: Problems with extended-Query logging code

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Problems with extended-Query logging code
Date: 2006-09-07 15:08:26
Message-ID: 5811.1157641706@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> I happened to notice that the recently added code to log Bind-message
>> parameters was printing garbage into my log. On investigation it turned
>> out to be trying to print an already-pfree'd string. That's fixable,

> Uh, can you show me where?

I didn't trace it down yet, but what I saw was garbage printed at
Execute time in an assert-enabled build. I think the bind-parameter
string that's being saved in the portal for Execute to print is not
copied into the portal's context. Since I want to get rid of that bit
anyway it didn't seem critical to identify the exact bug.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Albe Laurenz 2006-09-07 15:17:40 Re: [HACKERS] Fix linking of OpenLDAP libraries
Previous Message Strong, David 2006-09-07 14:59:47 Looking at Postgres 8.2