Re: Built-in connection pooling - Mailing list pgsql-hackers

From Christophe Pettus
Subject Re: Built-in connection pooling
Date
Msg-id CD9AEE4B-100C-4396-BB43-811B5A97361B@thebuild.com
Whole thread Raw
In response to Re: Built-in connection pooling  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: Built-in connection pooling  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Re: Built-in connection pooling  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
> On Apr 24, 2018, at 06:52, Merlin Moncure <mmoncure@gmail.com> wrote:
> Why does it have to be completely transparent?

Well, we have non-transparent connection pooling now, in the form of pgbouncer, and the huge fleet of existing
application-stackpoolers.  The main reason to move it into core is to avoid the limitations that a non-core pooler has. 

--
-- Christophe Pettus
   xof@thebuild.com



pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Minor comment update in execPartition.c
Next
From: Heikki Linnakangas
Date:
Subject: Re: Fsync request queue