| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Gerhard Lutz <gerhard(dot)lutz(at)mbtech-group(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5242: ODBC driver v8.4.1 crashed |
| Date: | 2009-12-15 17:21:50 |
| Message-ID: | 603c8f070912150921w311354c1ubbe68169d58ed8d3@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Dec 14, 2009 at 2:57 AM, Gerhard Lutz
<gerhard(dot)lutz(at)mbtech-group(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5242
> Logged by: Gerhard Lutz
> Email address: gerhard(dot)lutz(at)mbtech-group(dot)com
> PostgreSQL version: 8.4.1
> Operating system: Windows XP
> Description: ODBC driver v8.4.1 crashed
> Details:
>
> Hello,
> in my application the PostgreSQL ODBC driver v8.4.1 sometimes crashed when
> accessing a PostgreSQL v8.3.6 server.
> I want to read out data from a column of type "TEXT". I use a simple SQL
> query "SELECT prg FROM testdata WHERE id=1234".
> Inside the following C call
>
> rcode = ::SQLGetData(m_hStmt, nCol, SQL_C_CHAR, m_szString, nBufSize,
> &sdODataLength);
>
> the psqlodbc35w.dll crashes (probably depending on the column data).
> I've got Mini Dumps of these crashes. Just tell me if you need them.
>
> Do you already know something about this problem?
Since there has been no response here, I would try reposting this
problem report on pgsql-odbc. This list is technically for PostgreSQL
bugs proper, and it seems that the pgsql-odbc folks don't follow it
closely.
And to the list: can we PLEASE, PRETTY PLEASE add a note about this on
the bug submission page? I asked for this before and Tom concurred,
but I'm not aware that anything has been done about it. What do I
have to do to make this happen?
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-12-15 17:22:49 | Re: BUG #5242: ODBC driver v8.4.1 crashed |
| Previous Message | Robert Haas | 2009-12-15 17:18:28 | Re: statement_timeout is not cancelling query |