Обсуждение: Can't run current PostgreSQL
I am trying to run the latest version (supping source daily) and I get the
following error when I run psql.
Connection to database 'darcy' failed.
connectDB() failed: Is the postmaster running and accepting connections at 'UNIX Socket' on port '5432'?
Have I missed some change that I have to make? This is on the same
system as the server.
TIA.
--
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.
On Sat, 10 Jan 1998, D'Arcy J.M. Cain wrote:
> I am trying to run the latest version (supping source daily) and I get the
> following error when I run psql.
>
> Connection to database 'darcy' failed.
> connectDB() failed: Is the postmaster running and accepting connections at 'UNIX Socket' on port '5432'?
>
> Have I missed some change that I have to make? This is on the same
> system as the server.
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...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
> > I am trying to run the latest version (supping source daily) and I get the > following error when I run psql. > > Connection to database 'darcy' failed. > connectDB() failed: Is the postmaster running and accepting connections at 'UNIX Socket' on port '5432'? > > Have I missed some change that I have to make? This is on the same > system as the server. I have seen cases since the password changes that the postmaster does not start properly. If I start it from a script, it failes, but if I start it from the command line or gdb, it works. Haven't figured out why yet. -- Bruce Momjian maillist@candle.pha.pa.us