RE: PostgreSQL on Win/2K - Mailing list pgsql-cygwin

From Dave Page
Subject RE: PostgreSQL on Win/2K
Date
Msg-id 8568FC767B4AD311AC33006097BCD3D61A2D01@woody.vale-housing.co.uk
Whole thread Raw
In response to PostgreSQL on Win/2K  (Kian Parsee <kparsee@yahoo.com>)
Responses RE: PostgreSQL on Win/2K  (Kian Parsee <kparsee@yahoo.com>)
Re: PostgreSQL on Win/2K  (Jason Tishler <Jason.Tishler@dothill.com>)
List pgsql-cygwin

> -----Original Message-----
> From: Kian Parsee [mailto:kparsee@yahoo.com]
> Sent: 11 July 2001 14:58
> To: pgsql-cygwin@postgresql.org
> Subject: [CYGWIN] PostgreSQL on Win/2K
>
>
> Hi Everybody.  I'm trying to run Postgres7.1.2 on a
> Win/2K machine with Cygwin1.3.2-1.  I'm having no luck
> whatsoever.  I get the same result when I use the already
> built version that comes with cygwin, and when I build it
> myself.  The following commands all seem to work fine:
>
> ipc-daemon &
> initdb -D /usr/local/pgsql/data
> postmaster -i -D /usr/local/pgsql/data &
>
> However, when I try createdb, or psql, I get the
> following error:
>
> pq_flush: send() failed: Invalid argument
> pq_recvbuf: recv() failed: The descriptor is a file,
> not a socket
> psql: pqReadData() -- backend closed the channel
> unexpectedly.
>         This probably means the backend terminated
> abnormally
>         before or while processing the request.
>
>
>
> Now, I've got postgres working on a Win/NT machine
> with no problem.  Does anybody have any clue why I'm
> getting the above error on a Win/2K machine?
>
> Your help would be very appreciated.

Try setting the environment variable PGHOST=localhost or try using psql (or
createdb) with a command line like:

psql -h localhost template1

Either of these methods should make the client apps use tcp/ip rather than
Unix sockets.

hth, Regards, Dave.

pgsql-cygwin by date:

Previous
From: Kian Parsee
Date:
Subject: PostgreSQL on Win/2K
Next
From: "Robby Slaughter"
Date:
Subject: RE: ODBC calls seem surprisingly slow...