BUG #14146: Connection refused (0x0000274D/10061

The following bug has been logged on the website:

Bug reference: 14146
Logged by: BABU BALAKRISHNAN
Email address: bbabhu(at)me(dot)com
PostgreSQL version: 9.4.8
Operating system: Windows 7
Description:

hey guys im really got into this trouble, im not a technical expert in
postgres, but i do have a larger database on postgres. I cant able to
retrieve my database also,

suddenly today i cant able to connect my server. While i tried its says
something wrong about the port. below is the error message while i tried to
connect the server.
help me please. !!!

---

Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused (0x0000274D/10061) Is the
server running on host "localhost" (::1) and accepting TCP/IP connections on
port 5432? could not connect to server: Connection refused
(0x0000274D/10061) Is the server running on host "localhost" (127.0.0.1) and
accepting TCP/IP connections on port 5432?
If you encounter this message, please check if the server you're trying to
contact is actually running PostgreSQL on the given port. Test if you have
network connectivity from your client to the server host using ping or
equivalent tools. Is your network / VPN / SSH tunnel / firewall configured
correctly?
For security reasons, PostgreSQL does not listen on all available IP
addresses on the server machine initially. In order to access the server
over the network, you need to enable listening on the address first.
For PostgreSQL servers starting with version 8.0, this is controlled using
the "listen_addresses" parameter in the postgresql.conf file. Here, you can
enter a list of IP addresses the server should listen on, or simply use '*'
to listen on all available IP addresses. For earlier servers (Version 7.3 or
7.4), you'll need to set the "tcpip_socket" parameter to 'true'.
You can use the postgresql.conf editor that is built into pgAdmin III to
edit the postgresql.conf configuration file. After changing this file, you
need to restart the server process to make the setting effective.
If you double-checked your configuration but still get this error message,
it's still unlikely that you encounter a fatal PostgreSQL misbehaviour. You
probably have some low level network connectivity problems (e.g. firewall
configuration). Please check this thoroughly before reporting a bug to the
PostgreSQL community.