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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-01 23:46:24 | Re: Libpq free bug? (Was: [ODBC] IIS Postgres ASP ADO - Problem) |
Previous Message | Marko Ristola | 2005-08-01 21:12:47 | Re: Libpq free bug? (Was: [ODBC] IIS Postgres ASP ADO - Problem) |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-01 23:46:24 | Re: Libpq free bug? (Was: [ODBC] IIS Postgres ASP ADO - Problem) |
Previous Message | Greg Campbell | 2005-08-01 21:28:32 | Re: IIS Postgres ASP ADO - Problem |