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

From Henshall, Stuart - WCP
Subject RE: PostgreSQL on Win/2K
Date
Msg-id E2870D8CE1CCD311BAF50008C71EDE8E01F7460D@MAIL_EXCHANGE
Whole thread Raw
In response to PostgreSQL on Win/2K  (Kian Parsee <kparsee@yahoo.com>)
Responses Re: PostgreSQL on Win/2K  (Jason Tishler <Jason.Tishler@dothill.com>)
List pgsql-cygwin
Is localhost correctly referenced? Does psql -h 127.0.0.1 template1 work?
You could try having a look at port 5432 with a port scanner to see if its
open.
Maybe try shuting postgresql down and deleting /tmp/.s.PGSQL.5432 and
/tmp/.s.PGSQL.5432.lock file.
As a side note, has any one else had their text come out backwards in the
cygwin BASH while PostgreSQL has been heavily busy?
- Stuart

> -----Original Message-----
> From:    Kian Parsee [SMTP:kparsee@yahoo.com]
> Sent:    Wednesday, July 11, 2001 3:58 PM
> To:    Dave Page; pgsql-cygwin@postgresql.org
> Subject:    RE: [CYGWIN] PostgreSQL on Win/2K
>
> I tried both, and I'm still getting the same error
> message.
> --- Dave Page <dpage@vale-housing.co.uk> wrote:
> >
> >
> > > -----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.
>
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail
> http://personal.mail.yahoo.com/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly

pgsql-cygwin by date:

Previous
From: Kian Parsee
Date:
Subject: RE: PostgreSQL on Win/2K
Next
From: Jason Tishler
Date:
Subject: Re: initdb failure - postgres hangs with 100% CPU