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

From Tsunakawa, Takayuki
Subject RE: Built-in connection pooling
Date
Msg-id 0A3221C70F24FB45833433255569204D1F9449B6@G01JPEXMBYT05
Whole thread Raw
In response to Re: Built-in connection pooling  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Built-in connection pooling
List pgsql-hackers
From: Konstantin Knizhnik [mailto:k.knizhnik@postgrespro.ru]
Oracle, for example, you can create dedicated and non-dedicated backends.
> I wonder why we do not want to have something similar in Postgres.

Yes, I want it, too.  In addition to dedicated and shared server processes, Oracle provides Database Resident
ConnectionPooling (DRCP).  I guessed you were inspired by this.
 

https://docs.oracle.com/cd/B28359_01/server.111/b28310/manproc002.htm#ADMIN12348

BTW, you are doing various great work -- autoprepare, multithreaded Postgres, built-in connection pooling, etc. etc.,
aren'tyou?  Are you doing all of these alone?
 

Regards
Takayuki Tsunakawa




pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Should we add GUCs to allow partition pruning to be disabled?
Next
From: Michael Paquier
Date:
Subject: Re: Truncation failure in autovacuum results in data corruption(duplicate keys)