Re: ECPG: store own copy of the prepared statement name

From: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
To: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Meskes <meskes(at)postgresql(dot)org>
Cc: Hans-Juergen Schoenig <hs(at)cybertec(dot)at>
Subject: Re: ECPG: store own copy of the prepared statement name
Date: 2009-10-15 11:49:09
Message-ID: 4AD70C35.7010009@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Meskes írta:
> On Wed, Oct 14, 2009 at 06:37:43PM +0200, Boszormenyi Zoltan wrote:
>
>> the attached patch makes ECPG more robust
>> against applications that free() strings by storing
>> its own copy of the prepared statement name.
>>
>
> Please do not call strdup() directly in libecpg. Instead please use
> ecpg_strdup() which does all the error handling needed. I changed this and
> committed the patch. Thanks.
>
> Michael
>

Thanks, I will keep it in mind.

Best regards,
Zoltán Böszörményi

--
Bible has answers for everything. Proof:
"But let your communication be, Yea, yea; Nay, nay: for whatsoever is more
than these cometh of evil." (Matthew 5:37) - basics of digital technology.
"May your kingdom come" - superficial description of plate tectonics

----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
http://www.postgresql.at/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2009-10-15 13:07:09 Re: visual c++ compile error when included spi.h and trigger.h
Previous Message Itagaki Takahiro 2009-10-15 11:29:44 EXPLAIN BUFFERS