Postgres Pro
Downloads
Home   >   mailing lists

Re: ECPG: store own copy of the prepared statement name - Mailing list pgsql-hackers

From Michael Meskes
Subject Re: ECPG: store own copy of the prepared statement name
Date
Msg-id 20091015102124.GA31217@feivel.credativ.lan
Whole thread Raw
In response to ECPG: store own copy of the prepared statement name  (Boszormenyi Zoltan <zb@cybertec.at>)
Responses Re: ECPG: store own copy of the prepared statement name  (Boszormenyi Zoltan <zb@cybertec.at>)
List pgsql-hackers
Tree view 
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
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: meskes@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!

pgsql-hackers by date:

Previous
From: Itagaki Takahiro
Date:
Subject: EXPLAIN BUFFERS
Next
From: Boszormenyi Zoltan
Date:
Subject: Re: ECPG: store own copy of the prepared statement name