Re: Big number of connections

От: Chris Cogdon
Тема: Re: Big number of connections
Дата: ,
Msg-id: B2F62CE5-A0D5-4FBB-82B6-FB1EBBD81996@cogdon.org
(см: обсуждение, исходный текст)
Ответ на: Re: Big number of connections  (Alvaro Herrera)
Список: pgsql-performance

Скрыть дерево обсуждения

Big number of connections  (Jarek, )
 Re: Big number of connections  (Igor Neyman, )
  Re: Big number of connections  (Andrew Dunstan, )
   Re: Big number of connections  (Alvaro Herrera, )
    Re: Big number of connections  (Chris Cogdon, )
    Re: Big number of connections  (Karl Denninger, )
  Re: Big number of connections  (jarek, )
   Re: Big number of connections  (Jim Nasby, )
    Re: Big number of connections  ("Mike Sofen", )
     Re: Big number of connections  (Pavel Stehule, )
      Re: Big number of connections  (Moreno Andreo, )
       Re: Big number of connections  (Artem Tomyuk, )
        Re: Big number of connections  (Moreno Andreo, )
         Re: Big number of connections  (Artem Tomyuk, )
       Re: Big number of connections  (Pavel Stehule, )

Although somewhat academic, since pgboucer doesn’t support it (and might not ever), have a look at this ticket which, if it was ever supported, would give you what you needed:



On Mar 31, 2016, at 15:47, Alvaro Herrera <> wrote:

If they are going to keep the client connections open, they would need to
run pgbouncer in statement or transaction mode.

As I understand, in pgbouncer you cannot have connections that serve
different users.  If each individual requires its own database-level
user, pgbouncer would not help at all.

I would look seriously into getting rid of the always-open requirement
for connections.

— Chris Cogdon

В списке pgsql-performance по дате сообщения:

От: Alexandre de Arruda Paes
Дата:
Сообщение: Fast HashJoin only after a cluster/recreate table
От: jarek
Дата:
Сообщение: Re: Big number of connections