From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | DrakoRod <drakoflames(at)hotmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting |
Date: | 2017-06-29 17:22:04 |
Message-ID: | CAKFQuwb3NbVpe2Uh4vwkaiDN4oR3jrV-zvm-Vd+mX0NpxtZS7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jun 29, 2017 at 10:03 AM, DrakoRod <drakoflames(at)hotmail(dot)com> wrote:
> 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.
>
If you have lots of permanently maintained client sessions and cannot
change the client behavior you either need to try and get transaction
pooling working in a proxy pooling layer and point that clients to that OR
increase the number of simultaneous sessions your server will allow to some
number larger than the maximum possible concurrently connected clients.
And hope the server can handle the extra load.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Ilya Roublev | 2017-06-29 20:03:59 | Connecting matlab with postgresql |
Previous Message | DrakoRod | 2017-06-29 17:03:00 | Re: postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting |