RE: PostgreSQL on Win/2K

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Kian Parsee'" <kparsee(at)yahoo(dot)com>, pgsql-cygwin(at)postgresql(dot)org
Subject: RE: PostgreSQL on Win/2K
Date: 2001-07-11 14:10:51
Message-ID: 8568FC767B4AD311AC33006097BCD3D61A2D01@woody.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-cygwin

> -----Original Message-----
> From: Kian Parsee [mailto:kparsee(at)yahoo(dot)com]
> Sent: 11 July 2001 14:58
> To: pgsql-cygwin(at)postgresql(dot)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.

Responses

Browse pgsql-cygwin by date

  From Date Subject
Next Message Jason Tishler 2001-07-11 14:13:42 Re: Libpq.dll on MinGW, was Re: initdb failure - postgres hangs with 100% CPU
Previous Message Kian Parsee 2001-07-11 13:58:07 PostgreSQL on Win/2K