Обсуждение: PostgreSQL 7.2 Snapshot

Hi,

During my earlier discussion on the list with Jason re: initdb (7.2), I
mentioned that whilst ntsec made initdb work, I was having problems
connecting to the server though I thought this wan't Cygwin).

I've now tried every thing I can think of and still can't make a connection.
I have:

1) Checked $PGHOST & $PGDATA.
2) Made sure my PostgreSQL 7.1.3 is *not* running.
3) Checked pg_hba.conf.
4) Ensured that the postmaster is started with -i and remains running once
started.
5) Tried passing all options to psql including port, host & database.
6) Confirmed that running 'postgres.exe template1' gives me direct access to
the database.

I am running everything except cygipc (running as a service - any yes, it is
running!) from a bash session and yet still get the following from psql (and
similar errors as you'd expect from createdb or an ODBC app):

psql: connectDBStart() -- connect() failed: Connection refused
        Is the postmaster running (with -i) at 'localhost'
        and accepting connections on TCP/IP port 5432?

I do vaguely recall a thread on -patches discussing re-jigging of the code
that listens for connections and then forks a new process - could this have
been broken on Cygwin?

Regards, Dave.

--
Dave Page (dpage@postgresql.org)
pgAdmin Project Leader
http://pgadmin.postgresql.org/

Dave,

On Fri, Sep 28, 2001 at 08:48:10AM +0100, Dave Page wrote:
> I am running everything except cygipc (running as a service - any yes, it is
> running!) from a bash session and yet still get the following from psql (and
> similar errors as you'd expect from createdb or an ODBC app):
>
> psql: connectDBStart() -- connect() failed: Connection refused
>         Is the postmaster running (with -i) at 'localhost'
>         and accepting connections on TCP/IP port 5432?
>
> I do vaguely recall a thread on -patches discussing re-jigging of the code
> that listens for connections and then forks a new process - could this have
> been broken on Cygwin?

I just tried connecting with TCP/IP sockets as opposed to AF_UNIX sockets
with the same PostgreSQL 7.2 snapshot that I used previously and I was
able to connect without any problems.  Sorry, but I cannot reproduce
your problem.

Jason

> -----Original Message-----
> From: Jason Tishler [mailto:jason@tishler.net]
> Sent: 29 September 2001 13:35
> To: Dave Page
> Cc: 'pgsql-cygwin@postgresql.org'
> Subject: Re: [CYGWIN] PostgreSQL 7.2 Snapshot
>
>
> Dave,
>
> On Fri, Sep 28, 2001 at 08:48:10AM +0100, Dave Page wrote:
> > I am running everything except cygipc (running as a service
> - any yes,
> > it is
> > running!) from a bash session and yet still get the
> following from psql (and
> > similar errors as you'd expect from createdb or an ODBC app):
> >
> > psql: connectDBStart() -- connect() failed: Connection refused
> >         Is the postmaster running (with -i) at 'localhost'
> >         and accepting connections on TCP/IP port 5432?
> >
> > I do vaguely recall a thread on -patches discussing
> re-jigging of the
> > code that listens for connections and then forks a new
> process - could
> > this have been broken on Cygwin?
>
> I just tried connecting with TCP/IP sockets as opposed to
> AF_UNIX sockets with the same PostgreSQL 7.2 snapshot that I
> used previously and I was able to connect without any
> problems.  Sorry, but I cannot reproduce your problem.

Oh well. I'll check for a newer snapshot. Thanks for trying.

Regards, Dave.

Dave,

On Sat, Sep 29, 2001 at 01:45:58PM +0100, Dave Page wrote:
> > -----Original Message-----
> > From: Jason Tishler [mailto:jason@tishler.net]
> > I just tried connecting with TCP/IP sockets as opposed to
> > AF_UNIX sockets with the same PostgreSQL 7.2 snapshot that I
> > used previously and I was able to connect without any
> > problems.  Sorry, but I cannot reproduce your problem.
>
> Oh well. I'll check for a newer snapshot. Thanks for trying.

No problem -- sorry for the terse email yesterday.  I'm a little short
on time presently and will be off-net starting tomorrow for 5 days.

FYI, I'm using a Cygwin DLL built from CVS shortly after the 1.3.3
release.  Try using the latest Cygwin snapshot to see if that solves
the problem for you.

Jason