It may happen that the earlier postmaster-process didn't get killed
properly . I'd this issue some time back.
Try doing a "ps -A" and see if the postmaster is still showing up in the
process list. If it is, then the db was not truly shutdown. So kill the
process and try again. If you wont get the postmaster then do a
netstat -plunta | grep 5432
And see if the process is binding to 0 0.0.0.0 . If its binding to 0
0.0.0.0 then probably your sysadmin can help you out.
Thanx
Sidd
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Sunday, August 14, 2005 5:25 PM
To: Shilpa Tisgaonkar
Cc: pgsql-admin@postgresql.org; shilpatisgaonkar@yahoo.com
Subject: Re: [ADMIN] Getting an error in connection refused
"Shilpa Tisgaonkar" <shilpa.tisgaonkar@opensystemsinc.com> writes:
> I'm getting the following error
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" and accepting
> TCP/IP connections on port 5432?
Looks like the postmaster hasn't been started. See the PG
documentation...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
