Hi!
I don't have an answer for you. There maybe someone else on this list that
could help, though I think your best bet would be to ask the question again
on the pgsql-odbc list.
I posted it in pgsql-odbc list.
In pgsql odbc source code file connection.c: line 866
contains:
errprimary = PQr
On 2/23/20 1:06 AM, Andrus wrote:
Hi!
What does the log_error_verbosity setting in postgresql.conf show?
It is not set. postgresql.conf contains it default value from installation:
#log_error_verbosity = default # terse, default, or verbose messages
I changed it to
log_error_verbosi
Hi!
What does the log_error_verbosity setting in postgresql.conf show?
It is not set. postgresql.conf contains it default value from installation:
#log_error_verbosity = default# terse, default, or verbose messages
I changed it to
log_error_verbosity = verbose
but problem persists.
On 2/22/20 5:19 PM, Adrian Klaver wrote:
On 2/22/20 2:37 PM, Andrus wrote:
Hi!
I'm looking for a way to fix psqlODBC driver regression.
Starting at psqlODBC 09.05.0100 when psqlODBC driver uses libpq for all
operations (earlier versions used libpg only for authentication) ODBC client
does not
On 2/22/20 2:37 PM, Andrus wrote:
Hi!
I'm looking for a way to fix psqlODBC driver regression.
Starting at psqlODBC 09.05.0100 when psqlODBC driver uses libpq for all
operations (earlier versions used libpg only for authentication) ODBC
client
does not show error message details.
For example
Hi!
I'm looking for a way to fix psqlODBC driver regression.
Starting at psqlODBC 09.05.0100 when psqlODBC driver uses libpq for all
operations (earlier versions used libpg only for authentication) ODBC client
does not show error message details.
For example, users got only generic error messag
