[GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting - Mailing list pgsql-general

From DrakoRod
Subject [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting
Date
Msg-id 1498594257880-5968923.post@n3.nabble.com
Whole thread Raw
Responses Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting  (Melvin Davidson <melvin6925@gmail.com>)
Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Hi folks.

Today I had a problem with production's database PostgreSQL version 9.4.4.9.
The server have max_connections set to 200, but today I reviewed
pg_stat_activity and saw 199 active connections, obviously the server
rejected any new connection and the production stopped.

I saw another posts with a similar problems, but this was because the
pg_xlog was full or disk does'nt write, but the directory and disk  had no
problems.

I just canceled some SELECTs querys and the server returned to normality.
Now a monitoring activity of server and I can see some backends like this:

postgres  9737 23340  2 14:55 ?        00:00:15 postgres: dbname user
8.8.8.8[37082] idle in transaction
postgres  9741 23340  9 14:55 ?        00:00:47 postgres: dbname user
8.8.8.8[54286] idle in transaction

Any suggestions?



-----
Dame un poco de fe, eso me bastará.
Rozvo Ware Solutions
--
View this message in context:
http://www.postgresql-archive.org/postgres-dbname-dbuser-9-9-9-9-2222-PARSE-waiting-tp5968923.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: armand pirvu
Date:
Subject: [GENERAL] insert on conflict
Next
From: Melvin Davidson
Date:
Subject: Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting