| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Lev Kokotov <lev(dot)kokotov(at)instacart(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Include a connection pooler in Postgres |
| Date: | 2019-08-27 14:58:05 |
| Message-ID: | 58395722-5f4a-eb81-eda4-7538f9eb5cad@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8/27/19 7:35 AM, Lev Kokotov wrote:
> Hello,
>
> Since most web-facing clusters need to run tools like PgBouncer or Pgpool-II, why does Postgres not come with a connection pooler of its own?
Because PgBouncer and Pgpool exist, along with other options. Given an
excess of developers and/or developer time it would be nice to include
in core. To get an idea of what the developers are currently facing see
the latest Commitfest:
https://commitfest.postgresql.org/24/
>
> - Lev
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniele Varrazzo | 2019-08-27 15:04:02 | Re: Recomended front ends? |
| Previous Message | Holtgrewe, Manuel | 2019-08-27 14:43:18 | RE: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?) |