From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Can't run current PostgreSQL |
Date: | 1998-01-10 22:23:50 |
Message-ID: | m0xr9Jn-000009C@druid.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at){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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-01-10 22:45:10 | Re: [HACKERS] Can't run current PostgreSQL |
Previous Message | Edmund Mergl | 1998-01-10 20:01:27 | Re: [HACKERS] DefaultHost |