Re: How to fix 0xC0000005 exception in Postgres 9.0

From: "Andrus" <kobruleht2(at)hot(dot)ee>
To: "Justin" <zzzzz(dot)graf(at)gmail(dot)com>
Cc: "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>, "Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to fix 0xC0000005 exception in Postgres 9.0
Date: 2020-02-21 20:02:48
Message-ID: A5E46F8D8AEB49B092E97AF88BB3BAD1@dell2
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!

>Yes publish the ODBC logs

I send psqlodbc log from windows server to you.

I added and removed Debug=1 parameter from odbc conncetion string, ran
application as administrator.
Other errors

2020-02-21 21:27:30 EET ERROR: invalid memory alloc request size
4294967293
2020-02-21 21:27:30 EET STATEMENT: ;SELECT * FROM temptulemus offset 0
limit 900

and

2020-02-21 21:25:37 EET ERROR: could not open relation with OID 538386464
2020-02-21 21:25:37 EET STATEMENT: ;SELECT * FROM temptulemus offset 0
limit 900

also occured.

> Hello FOXPRO CODE
Yes.
Starting at psqlODBC 09.05.0100 when it uses libpq for all FoxPro does not
show error message details anymore.
I posted it it

https://stackoverflow.com/questions/54978713/how-to-get-psqlodbc-error-details-in-visual-foxpro

Maybe anybody has some idea how to get postgres error message details using
new psqlodbc drivers.
I looked into odbc description and havent found how error message details
are returned.

Andrus.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-02-21 20:22:40 Re: How to fix 0xC0000005 exception in Postgres 9.0
Previous Message Justin 2020-02-21 18:44:22 Re: How to fix 0xC0000005 exception in Postgres 9.0