Skip site navigation (1) Skip section navigation (2)

Re: Libpq free bug? (Was: [ODBC] IIS Postgres ASP ADO - Problem)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgsql-bugs(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org
Subject: Re: Libpq free bug? (Was: [ODBC] IIS Postgres ASP ADO - Problem)
Date: 2005-08-01 23:35:36
Message-ID: 26045.1122939336@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-odbc
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> Forwarded to -bugs in case it gets missed.
> This looks like it might be an issue to me, though I may well have
> overlooked something in my brief look at the code. 

There's nothing wrong with that code.  The only modifiable values in the
record are the "val" pointers, which are handled correctly.  See the
comment:

 * PQconninfoOptions[] is a constant static array that we use to initialize
 * a dynamically allocated working copy.  All the "val" fields in
 * PQconninfoOptions[] *must* be NULL.	In a working copy, non-null "val"
 * fields point to malloc'd strings that should be freed when the working
 * array is freed (see PQconninfoFree).

			regards, tom lane

In response to

pgsql-odbc by date

Next:From: Tom LaneDate: 2005-08-01 23:46:24
Subject: Re: Libpq free bug? (Was: [ODBC] IIS Postgres ASP ADO - Problem)
Previous:From: Greg CampbellDate: 2005-08-01 21:28:32
Subject: Re: IIS Postgres ASP ADO - Problem

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-08-01 23:46:24
Subject: Re: Libpq free bug? (Was: [ODBC] IIS Postgres ASP ADO - Problem)
Previous:From: Marko RistolaDate: 2005-08-01 21:12:47
Subject: Re: Libpq free bug? (Was: [ODBC] IIS Postgres ASP ADO - Problem)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group