PSequel Support | 18 Aug 06:19 2015

Bug in the SQLGetDiagRec function of psqlodbc

There seems to be a bug in the SQLGetDiagRec function - it always returns the oldest error message. For example, after I run two invalid queries, calling SQLGetDiagRec gives me the error message for the first query instead of the second one. However, according to the specs,

SQLGetDiagRec retrieves only the diagnostic information most recently associated with the handle specified in the Handle argument. If the application calls another ODBC function, except SQLGetDiagRec,SQLGetDiagField, or SQLError, any diagnostic information from the previous calls on the same handle is lost.

My psqlodbcw.so file was built from the HEAD of http://git.postgresql.org/git/psqlodbc.git using Homebrew on Mac OS X. Here is the code for demonstrating this issue:

#include <stdio.h>
#include <sql.h>
#include <sqlext.h>

void printError(SQLHANDLE handle) {
  char message[256];
  SQLSMALLINT i = 0;
  while (SQLGetDiagRec(SQL_HANDLE_DBC, handle, ++i, NULL, NULL, (SQLCHAR*)message, sizeof(message), NULL) != SQL_NO_DATA) {
    printf("%s\n", message);
  }
}

BOOL runQuery(SQLHSTMT stmt, char* query) {
  SQLRETURN ret = SQLExecDirect(stmt, (SQLCHAR*)query, SQL_NTS);
  printf("Query: %s\n", query);
  return SQL_SUCCEEDED(ret);
}

int main(int argc, const char * argv[]) {
  SQLHENV env;
  SQLHDBC dbc;
  SQLHSTMT stmt;

  SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &env);
  SQLSetEnvAttr(env, SQL_ATTR_ODBC_VERSION, (SQLPOINTER)SQL_OV_ODBC3, 0);
  SQLAllocHandle(SQL_HANDLE_DBC, env, &dbc);

  char* connStr = "Driver=/usr/local/Cellar/psqlodbc/HEAD/lib/psqlodbcw.so;Server=localhost;Database=postgres";
  if (SQLDriverConnect(dbc, NULL, (SQLCHAR*)connStr, SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT) != SQL_SUCCESS) {
    printf("Unable to connect to database\n");
    return 1;
  }

  SQLAllocHandle(SQL_HANDLE_STMT, dbc, &stmt);
  for (int i = 0; i < 3; ++i) {
    char query[50];
    sprintf(query, "SELECT * FROM t%d", i);
    if (!runQuery(stmt, query)) {
      printError(dbc); // this always prints 'ERROR: relation "t0" does not exist' - that's wrong!
    }
  }

  SQLDisconnect(dbc);
  SQLFreeHandle(SQL_HANDLE_STMT, stmt);
  SQLFreeHandle(SQL_HANDLE_DBC, dbc);
  SQLFreeHandle(SQL_HANDLE_ENV, env);
  return 0;
}
John Kew | 13 Aug 01:21 2015

Next Release?

I'm curious about the next release. It looks like a few of the folks who helped out with the previous releases haven't been active in a while so I wanted to figure out how we can move things along.


I'm also interested in making sure the patch mentioned in this message is merged into main or a derivation of the patch. I checked and it looks like it needs a bit of work to apply cleanly - and it needs some additional testing. 


   http://www.postgresql.org/message-id/543F0A50.4040106 <at> tpf.co.jp


There's a bit of work all-around; but I wanted to get the discussion going.


-John



Brian Sullivan | 10 Aug 21:03 2015

Creating an application that supports postgresql-odbc

Hello,

 

                I maintain a company application that queries various databases for predetermined information and saves it locally on the user’s computer in a neater format for upload to a server.  We support as many database types as possible and recently added the capability to support PostgreSQL but the connection to the database can only be established if the user has the drivers downloaded from: http://www.postgresql.org/ftp/odbc/versions/msi/

 

The project is built in VS2010.  Can you assist me in this effort?  How do I package your drivers in with my application?  The installation is a clickonce installation.

 

Thank you in advance,

 

Brian Sullivan | eTelligent Solutions, Inc.

(727) 202-1377 Direct | (727) 324-4026 Fax | (727) 322-4690 Main

bsullivan <at> etelligentsolutions.com

 

IAITAM Provider Member


http://www.etelligentsolutions.com  

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

 

Dmitry Pogorelov | 2 Aug 21:13 2015
Picon

PSQL iODBC driver on mac os x 10.10.3 (Yosemite)

Hi,

I've got postges 9.4 installed on Mac OS X 10.10.3 (Yosemite) I have access to it from psql and I have set up and filled a database I now want to access via ODBC - all on the localhost, no remote access involved. To get the 32 bit PSQL iODBC driver I've run the following command on the latest source code (psqlodbc-09.03.0400.tar.gz): 

./configure CFLAGS="-arch i386 -D ENABLE_MYLOG" --with-iodbc=/usr/local/iODBC --with-libpq=/Library/PostgreSQL/9.4

make

I've also built the latest version (3.52.10) of iODBC (https://github.com/openlink/iODBC) by the instruction from https://github.com/openlink/iODBC/blob/develop/README.MACOSX link (see method 1).

Further I copied the built in first step PSQL iODBC driver to /Library/ODBC/PSQL/bin/iODBC/ folder, I also added all necessaries libs:
1. iODBC from /Library/Frameworks/iODBC.framework/Versions/3.52/iODBC,
2. iODBCinst from /Library/Frameworks/iODBCinst.framework/Versions/3.52/iODBCinst
3. libpq.5.dylib from /Library/PostgreSQL/9.4/lib/libpq.5.7.dylib (renamed it to libpq.5.dylib)
4. libssl.1.0.0.dylib from /usr/local/Cellar/openssl/1.0.2/lib (installed openssl via brew)
 to /Library/ODBC/test/lib folder and changed paths to .dylib in built psql driver by the following commands:

install_name_tool -change libssl.1.0.0.dylib /Library/ODBC/PSQL/lib/libssl.1.0.0.dylib /Library/ODBC/PSQL/bin/iODBC/psqlodbcw.so

install_name_tool -change libpq.5.dylib /Library/ODBC/PSQL/lib/libpq.5.dylib /Library/ODBC/PSQL/bin/iODBC/psqlodbcw.so

install_name_tool -change /Library/Frameworks/iODBC.framework/Versions/3.52/iODBC /Library/ODBC/PSQL/lib/iODBC /Library/ODBC/PSQL/bin/iODBC/psqlodbcw.so

install_name_tool -change /Library/Frameworks/iODBCinst.framework/Versions/3.52/iODBCinst /Library/ODBC/PSQL/lib/iODBCinst /Library/ODBC/PSQL/bin/iODBC/psqlodbcw.so

I've also created odbc.ini and odbcinst.ini files in /Library/ODBC folder. The odbc.ini contains:

[ODBC Data Sources]

PSQL_Unicode_32           = PSQL iODBC Driver 32 bit (Unicode)

[PSQL_Unicode_32]

Driver           = /Library/ODBC/PSQL/bin/iODBC/psqlodbcw.so

ServerName       = 127.0.0.1

Port             = 5432

Database         = test_tables

Username         = postgres

Password         = sa

UpdatableCursors = false

The odbcinst.ini contains:

[ODBC Drivers]

PSQL iODBC Driver 32 bit (Unicode)            = Installed

[PSQL iODBC Driver 32 bit (Unicode)]

Driver = /Library/ODBC/PSQL/bin/iODBC/psqlodbcw.so

Setup  =

In the OpenLink ODBC Administrator I can see the configured odbc driver and the driver also passes test connection.
Further I installed LibreOffice 4.3.7 32 bit to check the PSQL Driver 32 bit. So when I tried to connect to PostgreSQL via PSQL iODBC driver I couldn't get list of tables though sql queries worked correctly (the problem was only in getting of list tables). After that I installed the latest version of Microsoft Excel 2016 on mac (Microsoft Office for mac is supplied as 32 bit so far), when I also tried to connect to PostgreSQL via PSQL iODBC driver the Excel just hanged though on Windows both LibreOffice of the same version and Excel worked correctly. Could you please help me to solve the problem related to LibreOffice (couldn't get list of tables) and Excel 2016?
 
Thank you in advance.

Best Regards
Dmitry Pogorelov
Christian Ullrich | 31 Jul 20:30 2015
Picon

Bugs related to getting <at> <at> identity

Hello,

as there have been ominous rumblings lately about making another 
release, I wanted to remind you that I reported two bugs on 23 April. 
One breaks  <at>  <at> identity entirely [1], the other makes it unreliable with 
INSERTs into schema-qualified tables [2].

I provided a patch for the second, but there has been no feedback at 
all, and it is possible that the first bug is not real but a mistake I 
made in building the driver from source.

[1] http://www.postgresql.org/message-id/mhaknj$e4g$1 <at> ger.gmane.org
[2] http://www.postgresql.org/message-id/mhalik$s8k$1 <at> ger.gmane.org

-- 
Christian Ullrich

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Jens Sorensen (Intuii | 25 Jul 13:20 2015

PSQLODBC.DLL - The (maximum) expected data length is 8000, while the returned data length is 9606.

Hello,

 

I’m stuck.

 

I’m trying to import data from PostgreSQL running on an Untangle appliance (Untangle.com) to SQL Server, but can’t seem to overcome an issue with the following error:

 

Msg 7347, Level 16, State 1, Line 7

OLE DB provider 'MSDASQL' for linked server '(null)' returned data that does not match expected data length for column '[MSDASQL].uri'. The (maximum) expected data length is 8000, while the returned data length is 9606.

 

Even after increasing the MaxLongVarcharSize as in the following select statement, I still get this same error with the value of 8000.

 

select * from openrowset('MSDASQL', 'Dsn=PostgreSQL35W;MaxLongVarcharSize=16000;', 'select * from reports.http_events')

 

I’ve also tried this one:

 

select * from openrowset('MSDASQL', 'Driver=PostgreSQL Unicode(x64);uid=postgres;Server=10.5.55.1;port=5432;database=uvm;MaxLongVarChar=16000;',

 

‘SELECT event_id

      ,time_stamp

      ,session_id

      ,client_intf

      ,server_intf

      ,c_client_addr

      ,s_client_addr

      ,c_server_addr

      ,s_server_addr

      ,c_client_port

      ,s_client_port

      ,c_server_port

      ,s_server_port

      ,policy_id

      ,username

      ,hostname

      ,request_id

      ,method

      ,uri

      ,host

      ,c2s_content_length

      ,s2c_content_length

      ,s2c_content_type

      ,adblocker_blocked

      ,adblocker_cookie_ident

      ,adblocker_action

      ,webfilter_reason

      ,webfilter_category

      ,webfilter_blocked

      ,webfilter_flagged

      ,sitefilter_reason

      ,sitefilter_category

      ,sitefilter_blocked

      ,sitefilter_flagged

      ,clam_clean

      ,clam_name

      ,virusblocker_clean

      ,virusblocker_name

from reports.http_events')

 

From ODBC setup:

 

 

 

From a “pg_dump” of schema:

 

--

-- Name: http_events; Type: TABLE; Schema: reports; Owner: postgres; Tablespace:

--

 

CREATE TABLE http_events (

    event_id bigint NOT NULL,

    time_stamp timestamp without time zone,

    session_id bigint,

    client_intf smallint,

    server_intf smallint,

    c_client_addr inet,

    s_client_addr inet,

    c_server_addr inet,

    s_server_addr inet,

    c_client_port integer,

    s_client_port integer,

    c_server_port integer,

    s_server_port integer,

    policy_id bigint,

    username text,

    hostname text,

    request_id bigint,

    method character(1),

    uri text,

    host text,

    c2s_content_length bigint,

    s2c_content_length bigint,

    s2c_content_type text,

    adblocker_blocked boolean,

    adblocker_cookie_ident text,

    adblocker_action character(1),

    webfilter_reason character(1),

    webfilter_category text,

    webfilter_blocked boolean,

    webfilter_flagged boolean,

    sitefilter_reason character(1),

    sitefilter_category text,

    sitefilter_blocked boolean,

    sitefilter_flagged boolean,

    clam_clean boolean,

    clam_name text,

    virusblocker_clean boolean,

    virusblocker_name text

);

 

 

Any advise appreciated!

 

Jens

 

 

 

 

Ramesh Reddy | 24 Jul 19:56 2015
Picon

Re: When will you be adding ISC_REQ_MUTUAL_AUTH to the ODBC dwSSPIFlags variable?

Thanks you Lindsay.

The root of the question after delving little bit more, we did not find any properties to enable "Mutual Authentication" when using GSSAPI with Windows ODBC driver. Can this be added to the code?

Thanks

Ramesh..

I have pg-odbc working with Windows sspi authentication.  There is a guide online [1] that describes the key element: you need to run the postgres service as a domain user that you've registered as a security principal for that machine. If you need a service name other than POSTGRES there is a GUC setting for krbsrvname; set that and a corresponding SPN.

The only weird behaviour I've noticed is that looking at security events in Windows event manager, after some time the client kerberos authentication reverts to NTLMv1. I suspect that might be a problem between the pg domain user and AD though.

Also, connections never seem to pool but there's probably a good security reason for that.

[1] https://wiki.postgresql.org/wiki/Configuring_for_single_sign-on_using_SSPI_on_Windows

On 22 Jul 2015 1:12 am, "Ramesh Reddy" <rareddy <at> redhat.com> wrote:
Has any one have working solution that has kerberos authentication working on windows based pg-odbc driver? We believe the below flag is required for it to work correctly, can anybody weigh in options we have in terms of setting this flag with out code modification. We are also looking to build locally to verify the solution.

Thanks

Ramesh..

----- Original Message -----
> We need mutual authentication via ODBC, looking into the psqlODBC driver to
> find where the Kerberos connection was getting created.  Here in sspisvcs.c
> the PerformKerberosEtcClientHandshake contains the set of SSPI flags being
> set on the request (held in the dwSSPIFlags variable).
> This set is missing the flag required for mutual authentication
> (ISC_REQ_MUTUAL_AUTH).  Can this be added to your ODBC driver?
>
> --
> Regards,
> Debbie Steigner
> Red Hat Global Support Services
> Principal Technical Support Engineer
>
>
>
> --
> Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-odbc
>


--
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Jean-Marc Guazzo | 23 Jul 04:05 2015
Picon

Materialized Views

Hi,

Materialized Views aren't visible when I try to link them with MS Access, MS Excel or LibreOffice Base.

I guess that's because the ODBC driver doesn't return this information...

Can you tell me whether there will be some adjustement in the next version of the odbc driver regarding the MVs ?

Thanks.

JM.
Stefan Viljoen | 22 Jul 10:06 2015
Picon

Re: Postgres 9.4 + unixODBC on Centos 6.5 problem connecting localhost postgres instance with isql ODBC commandline client

Hi Adrian

Thanks for replying!

>> Hi List
>>
>> The plot thickens - I have now resorted to doing a tcpdump of the 
>> postgres port and then trying to connect via isql.
>>
>> The tcpdump command used was
>>
>> ---
>> tcpdump -vvvvv -x -X -s 65535 -i lo 'port 5432' -w post.pcap
>> ---
>>
>> This has revealed that in the post.pcap file (even just viewing the 
>> raw packet data with vi in the terminal) that the REASON postgress 
>> keeps rejecting isql login attempts is that isql apparently passes the 
>> database name only partially, or corrupts it randomly...

>Not sure, but here is what I see.

>First on my machine openSUSE 13.1

>unixODBC 2.3.1-3.1.2

Ok that is much more recent than my unixODBC as provided by the official
Centos 6.5 repositories, mine is unixODBC 2.2.14, even after a 

yum update unixodbc

>psqlodbc 09.03.0400

See below, I have this same 0400 version installed via yum from the
repository URL indicated below.

>odbcinst.ini

>[Postgres]
>Description             =
>Driver          = /usr/local/lib/psqlodbcw.so
>Driver64                = /usr/lib
>Setup           = /usr/lib/unixODBC/libodbcdrvcfg1S.so
>Setup64         = /usr/lib
>UsageCount              = 1
>CPTimeout               =
>CPReuse         =

>[ODBC]
>Trace           = No
>TraceFile               = /tmp/sql.log
>ForceTrace              = No
>Pooling         = No

Ok, I changed my driver to refer to psqlodbcw.so, NOT psqlodbc.so.

>odbc.ini

>[Production]
>Description             = Postgres
>Driver          = Postgres
>Host            = localhost
>Database                = production
>Port            =

Ok, I lacked a "Host" line (having a "ServerName=localhost" line instead) so
I added a "Host" line like this one above...

>aklaver <at> panda:~> isql -v Production
>+---------------------------------------+
>| Connected!                            |
>Where Production is pointing at a 9.4 database.

>I know we are not talking apples to apples, but at least it proves it is
possible.

Agreed.

>Now my observations.

>1) In my odbcinst.ini the Driver being pointed to is psqlodbcw.so instead
of psqlodbc.so in your odbcinst.ini. This leads to

Ok, I changed mine to psqlodbcw.so as well. No change.

>2) In your original post you have:

># yum list installed | grep postgres

>postgresql94.x86_64     9.4.4-1PGDG.rhel6
>postgresql94-contrib.x86_64
>postgresql94-devel.x86_64
>postgresql94-docs.x86_64
>postgresql94-libs.x86_64
>postgresql94-odbc.x86_64
>postgresql94-odbc-debuginfo.x86_64
>postgresql94-server.x86_64

Correct.

>Yet the Postgres yum repo:

>http://yum.postgresql.org/9.4/redhat/rhel-6-x86_64/

>has

>postgresql94-odbc-09.03.0300-1PGDG.rhel6.x86_64.rpm

Ok...

>So is it possible you have a version mismatch in the Postgres ODBC driver
and the Postgres server?

Ok, this is completely possible...

>I may have missed it, but do you know what version of psqlodbc you are
using or more to the point where is postgresql94-odbc.x86_64 is coming from?

I have

postgresql94-odbc-09.03.0400-1PGDG.rhel6.x86_64

e. g. I have the 0400 version like you have.

postgresql94-odbc.x86_64 is coming from the above URL you listed -
yum.postgresql.org/9.4/redhat/rhel-6-x86_64/

I know this due to how I installed Postgres 9.4 on my Centos 6.5 box:

- I edited /etc/yum.repos.d/CentOS-Base.repo and added a line

exclude=postgresql*

to the [base] and [updates] sections of CentOS-Base.repo

- I added a file

pgdg-94-centos.repo

to /etc/yum.repos.d

- This file contains

---
[pgdg94]
name=PostgreSQL 9.4 $releasever - $basearch
baseurl=http://yum.postgresql.org/9.4/redhat/rhel-$releasever-$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG-94

[pgdg94-source]
name=PostgreSQL 9.4 $releasever - $basearch - Source
failovermethod=priority
baseurl=http://yum.postgresql.org/srpms/9.4/redhat/rhel-$releasever-$basearc
h
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG-94
---

- I then ran 

yum install postgresql94
yum install postgresql94-odbc
yum install postgresql94-devel
yum install postgresql94-libs
yum install postgresql94-contrib
yum install postgresql94-docs

to install postgres.

So it appears my problem is an old unixODBC installation?

Should I uninstall the yum ODBC package in Centos 6.5 and try to compile and
install the current unixODBC version from source?

Wonder why the latest MariaDB is working fine with the 2.2 version of
unixODBC I have, while postgres 9.4 won't....

Thanks for the help.

Regards

Stefan

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Stefan Viljoen | 21 Jul 10:25 2015
Picon

Re: Postgres 9.4 + unixODBC on Centos 6.5 problem connecting localhost postgres instance with isql ODBC commandline client

Hi List

The plot thickens - I have now resorted to doing a tcpdump of the postgres
port and then trying to connect via isql.

The tcpdump command used was

---
tcpdump -vvvvv -x -X -s 65535 -i lo 'port 5432' -w post.pcap
---

This has revealed that in the post.pcap file (even just viewing the raw
packet data with vi in the terminal) that the REASON postgress keeps
rejecting isql login attempts is that isql apparently passes the database
name only partially, or corrupts it randomly...

E. g. I tried this five or six times and each time, the packets sent from
unixODBC / isql binary, specifies the string

asteriskcdrdb

which denotes the database name to postgress (and therefore is critical to
control login) as

&%% <at> %!db
*&#! <at> #drdb
! <at> &&%$idb

etc. and sometimes mixed / along with some other ASCII crud I cannot
duplicate here.

SSL is most definitely off so this cannot be encryption?

The STRANGE thing is I can spot the username (asteriskcdruser) in the packet
data and that is ALWAYS correct and uncorrupted, and is always passed as
"asteriskcdruser".

But the database name is -always- corrupted that is sent to port 5432 from
isql to login to postgress.

So if I do with isql

---
isql -v pgdb-cdr asteriskcdruser pword
---

In effect I try to login to postgress with

*&#! <at> #drdb

(as indicated by the packet data)  which is of course a database that does
not exist, nor is there a role that matches "asteriskcdruser" for such a
database.

From there the error

[S1000][unixODBC]The database does not exist on the server
or user authentication failed.
[ISQL]ERROR: Could not SQLConnect

which is completely logical as I'm trying to log into non-existent databases
as passed over ODBC from isql, no?

Any thoughts? How can this be fixed?

ODBC connections on the same box over the lo interface to MySQL keep working
100% - wonder why unixODBC is corrupting the database name, but ONLY when
passing it to Psql-odbc?

Or am I completely barking up the wrong tree?

Thanks

Stefan

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Stefan Viljoen | 21 Jul 09:31 2015
Picon

Re: Postgres 9.4 + unixODBC on Centos 6.5 problem connecting localhost postgres instance with isql ODBC commandline client

Hi List

With the new increased verbosity I managed to turn on, I've found something
interesting.

This was my definition in /etc/odbc.ini:

---
[ODBC Data Sources]
pgdb=PostgreSQL

[pgdb-cdr]
Driver                  = /usr/pgsql-9.4/lib/psqlodbc.so
ServerName=/tmp
Port=5432
UserName=asteriskcdruser
Password=1ndestruc#
Database=asteriskcdrdb
ReadOnly=No
Protocol=9.4
Trace=Yes
TraceFile=/tmp/odbc.log
ForceTrace=Yes
ConnSettings=
DSN=pgdb
ServerType=Postgres
Debug=1
DebugFile=/var/log/postgresql_debug.log
---

running

---
isql -v pgdb-cdr dbuser pass
---

gives in pg_log/postgresql-Tue.log the relevant error

---
< 2015-07-21 09:04:35.850 SAST >LOCATION:  PerformAuthentication,
postinit.c:258
< 2015-07-21 09:04:35.856 SAST >LOG:  08006: could not send data to client:
Broken pipe
---

However, removing these two lines from /etc/odbc.ini

---
DSN=pgdb
ServerType=Postgres
---

changes the logged output to this

---
< 2015-07-21 09:21:24.018 SAST >LOG:  00000: connection received:
host=[local]
< 2015-07-21 09:21:24.018 SAST >LOCATION:  BackendInitialize,
postmaster.c:4007
< 2015-07-21 09:21:24.019 SAST >LOG:  00000: connection authorized:
user=asteriskcdruser database=asteriskcdrdb
< 2015-07-21 09:21:24.019 SAST >LOCATION:  PerformAuthentication,
postinit.c:258
< 2015-07-21 09:21:24.022 SAST >LOG:  00000: disconnection: session time:
0:00:00.004 user=asteriskcdruser database=asteriskcdrdb host=[local]
< 2015-07-21 09:21:24.022 SAST >LOCATION:  log_disconnections,
postgres.c:4511
---

e. g. now the "broken pipe" error is gone, but I just get a virtually
instant disconnection.

The isql output remains the same:

---
# isql -v pgdb-cdr dbuser dbname
[S1000][unixODBC]The database does not exist on the server
or user authentication failed.
[ISQL]ERROR: Could not SQLConnect
---

but it appears that the REASON is now gone, e. g. no "broken pipe" logged by
Postgres?

This mean anything to anybody?

Thanks

Stefan

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc


Gmane