I tried both, and I'm still getting the same error
--- Dave Page <dpage(at)vale-housing(dot)co(dot)uk> wrote:
> > -----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
> > Win/2K machine with Cygwin1.3.2-1. I'm having no
> > whatsoever. I get the same result when I use the
> > built version that comes with cygwin, and when I
> build it
> > myself. The following commands all seem to work
> > 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
> > 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
> > 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.
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
In response to
pgsql-cygwin by date
|Next:||From: Jason Tishler||Date: 2001-07-11 15:01:24|
|Subject: Re: initdb failure - postgres hangs with 100% CPU|
|Previous:||From: Dave Page||Date: 2001-07-11 14:35:31|
|Subject: RE: ODBC calls seem surprisingly slow...|