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

From DrakoRod
Subject Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting
Date
Msg-id 1498755780674-5969262.post@n3.nabble.com
Whole thread Raw
In response to Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting
Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting
List pgsql-general
To expand information, the application are written in Grails on wildfly with
pool connections.

I didn't have time to check pg_locks with detail, I'll configure the
connections logs to monitoring those.

I can't close connections on the application side. How I close connections
on the database side? With pg_terminate_backend, pg_cancel_backend or exists
other function? I didn't want terminate backends because all connections
state was active.

I refer only to "idle" because almost in every database that I've saw the
application doesn't close correctly the connections. If are "idle in
transaction" is not normal.

Your right Adrian, I need to know why the connections are not closing
properly.

I can't apply idle_in_transation_session_timeout because the version of
PostgreSQL is 9.4.4 and the paramater not yet i'ts included. But sounds good
the upgrade.

Thanks for your help!




-----
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-tp5968923p5969262.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [GENERAL] 9.6 parameters messing up my 9.2 pg_dump/pg_restore
Next
From: "David G. Johnston"
Date:
Subject: Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting