From: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
To: Byron Nikolaidis <byronn@insightdist.com>
Cc: applixware-list@applix.com, Postgres Interfaces Mailing List <pgsql-interfaces@postgresql.org>
Subject: Re: AWL: postgres odbc woes, continued .......
Date: Fri, 15 Jan 1999 15:22:04 +0000
Message-ID: <369F5D1C.986EAFFA@alumni.caltech.edu> (raw)
References: <369D5D0E.AA522E2C@quoll.com>
<369EA745.BA3B2E5C@alumni.caltech.edu>
<369F4F54.B760B753@insightdist.com>
> 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.
I copied the older version's source code to the new tree and it worked
fine. No other changes, and I left postmaster running in between these
tests.
Are there any things to look at that a successful psql would not be
testing? I've also tried psql -h localhost...
- Tom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: lockhart@alumni.caltech.edu, byronn@insightdist.com
Subject: Re: AWL: postgres odbc woes, continued .......
In-Reply-To: <369F5D1C.986EAFFA@alumni.caltech.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox