| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | eric(dot)hill(at)jmp(dot)com |
| Cc: | PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #11608: ODBC driver crashes after wrong password entered |
| Date: | 2014-10-09 00:45:44 |
| Message-ID: | CAB7nPqSX_E8yKSb=jVCi7XXANVb_8bXxb-cNRwaXrCa4diWVBA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-odbc |
On Thu, Oct 9, 2014 at 2:54 AM, <eric(dot)hill(at)jmp(dot)com> wrote:
> This is more about your 64-bit ODBC driver than the PostgreSQL database
> itself.
>
This is more adapted on the pgsql-odbc list.
> We are using version 9.03.03 of your 64-bit ODBC driver. We are finding
> that after SQLDriverConnect() with a bad password, the driver becomes
> unstable, and a second call to SQLDriverConnect() can (but does not always)
> crash with an access violation. I have not tried the 32-bit driver to see
> if that replicates the problem, which means I also haven't tried other
> products that support ODBC, because I don't know of any other 64-bit
> products with ODBC support.
>
This should be easy to reproduce. Have you seen that on Linux/Unix as well.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-10-09 13:52:47 | Re: BUG #10675: alter database set tablespace and unlogged table |
| Previous Message | Amjith Ramanujam | 2014-10-08 20:47:47 | Client deadlocks when connecting via ssl |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Inoue, Hiroshi | 2014-10-10 00:16:06 | Re: Time for a new release? |
| Previous Message | eric.hill | 2014-10-08 17:54:46 | BUG #11608: ODBC driver crashes after wrong password entered |