From: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
---|---|
To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Built-in connection pooling |
Date: | 2018-04-17 17:09:30 |
Message-ID: | CANNMO+K_FzaetEM4LLV4YnEnwjECc71etsPMYLAbOXQLmQtuGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg스포츠 토토 사이트SQL |
Understood.
One more question. Have you considered creation of pooling tool as a
separate, not built-in tool, but being shipped with Postgres — like psql is
shipped in packages usually called “postgresql-client-XX” which makes psql
the default tool to work in terminal? I constantly hear opinion from
various users, that Postgres needs “default”/official pooling tool.
вт, 17 апр. 2018 г. в 0:44, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>:
>
>
> On 13.04.2018 19:07, Nikolay Samokhvalov wrote:
>
> On Fri, Apr 13, 2018 at 2:59 AM, Konstantin Knizhnik <
> k(dot)knizhnik(at)postgrespro(dot)ru> wrote:
>>
>> Development in built-in connection pooling will be continued in
>> https://github.com/postgrespro/postgresql.builtin_pool.git
>> I am not going to send new patches to hackers mailing list any more.
>>
>
> Why?
>
>
> Just do not want to spam hackers with a lot of patches.
> Also since I received few feedbacks in this thread, I consider that this
> topic is not so interesting for community.
>
> Please notice that built-in connection pool is conn_pool branch.
>
>
> --
> Konstantin Knizhnik
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2018-04-17 17:23:13 | Re: WIP: a way forward on bootstrap data |
Previous Message | Tom Lane | 2018-04-17 16:57:46 | pgindent run soon? |