PostgreSQL Error: server closed the connection unexpectedly

pgadminpostgresqlpostgresql-9.0

I cannot connect to PostgreSQL server from PgAdmin III , so I get this error:

Error connecting to the server: server closed the connection
unexpectedly

This probably means the server terminated abnormally before or while
processing the request.

I get the same error when I try connecting from psql.

I have got this error 2 days ago but after restarting the computer the problem disappears , but this time I have restarted it too many times vainly.

I'm using PostgreSQL 9.0.5 on windows 7 with ArcSDE 10.1 (Arcgis Spatial Database add-on), I have deactivated the antivirus and firewall.

I have tried to reinstall PgSQL but the problem persists.

How I can connect to my Pgsql service and get rid of this error?

Best Answer

It looks like broken data file or broken indexes. If this problem grows, then it can shows some deep system problems - problems with hw (memory, CPU), os (antivirus)... Try to use a commands executed from command prompt for database access repairing a) reindexdb - refresh all indexes, b) pg_dump - recheck a readability of data files.

Related Solutions

Postgresql – PgAdmin III – How to connect to database when password is empty

I can connect to my postgres instance from pgAdmin III without a password for any user including superusers such as postgres.

Because you are connecting ok from another client, there is no reason you should not be able to connect from pgAdmin if they are on the same workstation - unless some firewall rule on the client itself is allowing one program but not another.

If the problem is specific to this client, you may need to change one or more of:

pg_hba.conf

host    sa    all         192.168.0.nnn/32     trust

postgresql.conf

listen_addresses = '*'

the firewall on your postgres server, eg iptables:

-A INPUT -s 192.168.0.nnn -m state --state NEW -j ACCEPT

But I recommend you don't do any of this. The manual says the following with good reason:

trust authentication is only suitable for TCP/IP connections if you trust every user on every machine that is allowed to connect to the server by the pg_hba.conf lines that specify trust. It is seldom reasonable to use trust for any TCP/IP connections other than those from localhost (127.0.0.1).

Instead, consider either:

using a password and md5 identification
tunnelling port 5432 over ssh

PostgreSQL not working, pgAdmin always says server not listening

Since you installed multiple versions of PostgreSQL, there is a good chance your cluster is running on a different port than 5432. Additional clusters automatically use the next free port unless instructed otherwise. Like 5433, 5434 etc.

Check your setting in postgresql.conf to find out and connect to the proper port. postgresql.conf is usually installed in your data directory, which in turn is defined in pg_env.bat, usually located here

C:\Program Files\PostgreSQL\<version>\pg_env.bat

Default location of the data directory:

C:\Program Files\PostgreSQL\<version>\data\postgresql.conf

Where <version> is 9.1 or 9.2 in your case.
Base directory varies according to your version of Windows.

Obviously initdb fails to create a database cluster. Read the chapter in the manual to get a grip on initdb. Maybe a problem with missing privileges?

Here is a closely related question with a solution.

Best Answer

Related Solutions

Postgresql – PgAdmin III – How to connect to database when password is empty

PostgreSQL not working, pgAdmin always says server not listening

Related Question