Sender: tgl@mythos.jpl.nasa.gov
Message-ID: <369F5D1C.986EAFFA@alumni.caltech.edu>
Date: Fri, 15 Jan 1999 15:22:04 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Organization: Caltech/JPL
MIME-Version: 1.0
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 .......
References: <369D5D0E.AA522E2C@quoll.com>
	<369EA745.BA3B2E5C@alumni.caltech.edu>
	<369F4F54.B760B753@insightdist.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> 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