Re: [HACKERS] Can't run current PostgreSQL - Mailing list pgsql-hackers

From darcy@druid.net (D'Arcy J.M. Cain)
Subject Re: [HACKERS] Can't run current PostgreSQL
Date
Msg-id m0xr9Jn-000009C@druid.net
Whole thread Raw
List pgsql-hackers
Thus spake The Hermit Hacker
> > connectDB() failed: Is the postmaster running and accepting connections at 'UNIX Socket' on port '5432'?
>     New default startup disabled TCP/IP connections, using Unix Domain Sockets
> exclusively.  If PGHOST/PGPORT are set, then the "frontends" try to use TCP/IP
> vs Unix Domain, and will therefore fail.  To get the old behaviour, startup
> postmaster with the -i option to turn TCP/IP connections back on again...

Hmmm.  I saw that discussion but I didn't think it applied to me because
I don't run it over the network.  So if I unset PGHOST/PGPORT then it
should work?

I tried this and it wasn't set.  I tried setting it and it still didn't
work.  So, so far I have tried;

  With and without PGHOST/PGPORT defined
  With and without -i flag

Something else?

--
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 424 2871     (DoD#0082)    (eNTP)   |  what's for dinner.

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Re: subselects
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Can't run current PostgreSQL