Skip site navigation (1) Skip section navigation (2)

Re: AWL: postgres odbc woes, continued .......

From: Byron Nikolaidis <byronn(at)insightdist(dot)com>
To: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: applixware-list(at)applix(dot)com, Postgres Interfaces Mailing List <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: AWL: postgres odbc woes, continued .......
Date: 1999-01-15 14:23:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces

Thomas G. Lockhart wrote:

> > Any thoughts would be greatly appreciated.
> I'm having trouble running the development tree version of psqlODBC.
> Picking up the odbc source code from the v6.4 Postgres tarball and
> inserting it into src/interfaces/odbc gives me back a driver which seems
> to work.
> Byron, do you have any ideas on what might have changed? I vaguely
> recall that the newest code is using v6.4 protocol, and the v6.4 tarball
> code was using the v6.3.2 protocol?? I've enclosed my log files.
>                       - Tom
>   ------------------------------------------------------------------------
> globals.extra_systable_prefixes = 'dd_;'
> CC_connect: entering...
> CC_connect(): DSN = 'Test', server = 'localhost', port = '', database = 'test', username = 'tgl', password='no$way'
> connecting to the server socket...
> connection to the server socket failed.
> CONN ERROR: func=SQLConnect, desc='Error on CC_connect', errnum=101, errmsg='Could not connect to the server'
> **** SQLError: henv=0, hdbc=134613032, hstmt=0
> calling CC_get_error
> enter CC_get_error
> enter CC_create_errormsg
> msg = 'Could not connect to the server'
> exit CC_create_errormsg
> exit CC_get_error
> CC_get_error: status = 101, msg = #Could not connect to the server;
> Could not connect to remote socket.#
>   ------------------------------------------------------------------------
> DSN info: DSN='Test',server='localhost',port='5432',dbase='test',user='tgl',passwd='no$way'
>           readonly='0',protocol='',showoid='',fakeoidindex='',showsystable=''
>           conn_settings=''
>           translation_dll='',translation_option=''
> conn = 134613032, SQLConnect(DSN='Test', UID='tgl', PWD='no$way')
> Global Options: Version='06.40.0002', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
>                 disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
>                 text_as_longvarchar=0, unknowns_as_longvarchar=0, bools_as_char=1
>                 extra_systable_prefixes='dd_;', conn_settings=''
> CONN ERROR: func=SQLConnect, desc='Error on CC_connect', errnum=101, errmsg='Could not connect to the server'
>             ------------------------------------------------------------
>             henv=134613016, conn=134613032, status=0, num_stmts=16
>             sock=134619360, stmts=134627608, lobj_type=-999
>             ---------------- Socket Info -------------------------------
>             socket=-1, reverse=0, errornumber=4, errormsg='Could not connect to remote socket.'
>             buffer_in=134619400, buffer_out=134623504
>             buffer_filled_in=0, buffer_filled_out=0, buffer_read_in=0

This is a physical socket connection problem.  The Socket Info (above) shows errornumber=4, which is a failure in the connect()
system call.    At this point in communications, protocol has not have come into play yet.

I would suggest checking to see if the postmaster is running with -i, and can connect from the machine, and all that network jazz.


In response to


pgsql-interfaces by date

Next:From: Thomas G. LockhartDate: 1999-01-15 15:22:04
Subject: Re: AWL: postgres odbc woes, continued .......
Previous:From: Stefan HornburgDate: 1999-01-15 14:05:13
Subject: make test fails for DBD::Pg

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group