Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1lGhfa-0002bb-UX
	for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Mar 2021 12:29:02 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1lGhfZ-0008L6-Uw
	for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Mar 2021 12:29:01 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ayden@gera.co.nz>)
	id 1lG3aS-00033S-07
	for pgsql-hackers@lists.postgresql.org; Sat, 27 Feb 2021 17:41:04 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by makus.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <ayden@gera.co.nz>)
	id 1lG3aO-00008e-Po
	for pgsql-hackers@postgresql.org; Sat, 27 Feb 2021 17:41:02 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id 9C30924A68823
	for <pgsql-hackers@postgresql.org>; Sat, 27 Feb 2021 10:40:58 -0700 (MST)
Date: Sat, 27 Feb 2021 10:40:58 -0700 (MST)
From: AJG <ayden@gera.co.nz>
To: pgsql-hackers@postgresql.org
Message-ID: <1614447658602-0.post@n3.nabble.com>
In-Reply-To: <20200301083601.ews6hz5dduc3w2se@alap3.anarazel.de>
References: <20200301083601.ews6hz5dduc3w2se@alap3.anarazel.de>
Subject: Re: Improving connection scalability: GetSnapshotData()
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

Hi,

Greatly appreciate if you could please reply to the following questions as
time allows.

I have seen previous discussion/patches on a built-in connection pooler. How
does this scalability improvement, particularly idle connection improvements
etc, affect that built-in pooler need, if any?


Same general question about an external connection pooler in general in
Production? Still required to route to different servers but no longer
needed for the pooling part. as an example.


Many Thanks!





--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html