Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting
Дата
Msg-id CAKFQuwb3NbVpe2Uh4vwkaiDN4oR3jrV-zvm-Vd+mX0NpxtZS7w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting  (DrakoRod <drakoflames@hotmail.com>)
Список pgsql-general
Дерево обсуждения
On Thu, Jun 29, 2017 at 10:03 AM, DrakoRod <drakoflames@hotmail.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.

В списке pgsql-general по дате отправления:

Предыдущее
От: DrakoRod
Дата:
Сообщение: Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting
Следующее
От: Ilya Roublev
Дата:
Сообщение: [GENERAL] Connecting matlab with postgresql