Re: Built-in connection pooler

From: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
To: Ryan Lambert <ryan(at)rustprooflabs(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Dimitri Fontaine <dim(at)tapoueh(dot)org>
Subject: Re: Built-in connection pooler
Date: 2019-07-31 08:39:47
Message-ID: 9ba4e22d-2eac-5ffe-a9c4-19cb698d2af8@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 26.07.2019 19:20, Ryan Lambert wrote:
>
> > PgPRO EE version of connection pooler has "idle_pool_worker_timeout"
> > parameter which allows to terminate idle workers.
>
> +1
>

I have implemented idle_pool_worker_timeout.
Also I added _idle_clients and n_idle_backends fields to proxy statistic
returned by pg_pooler_state() function.

--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Attachment Content-Type Size
builtin_connection_proxy-15.patch text/x-patch 140.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Evgeny Efimkin 2019-07-31 08:54:18 Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Previous Message Amit Langote 2019-07-31 08:17:09 Re: Problem with default partition pruning