Date: Mon, 1 Mar 2021 09:49:47 -0300 (BRT)
From: luis.roberto@siscobra.com.br
To: AJG <ayden@gera.co.nz>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Message-ID: <486489735.28495535.1614602987743.JavaMail.zimbra@siscobra.com.br>
In-Reply-To: <1614447658602-0.post@n3.nabble.com>
References: <20200301083601.ews6hz5dduc3w2se@alap3.anarazel.de>
 <1614447658602-0.post@n3.nabble.com>
Subject: Re: Improving connection scalability: GetSnapshotData()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Thread-Topic: Improving connection scalability: GetSnapshotData()
Thread-Index: AIDrhY+o/AVMiuV74U6OruGAmbgFlQ==
Precedence: bulk


----- Mensagem original -----
> De: "AJG" <ayden@gera.co.nz>
> Para: "Pg Hackers" <pgsql-hackers@postgresql.org>
> Enviadas: S=C3=A1bado, 27 de fevereiro de 2021 14:40:58
> Assunto: Re: Improving connection scalability: GetSnapshotData()

> Hi,

> Greatly appreciate if you could please reply to the following questions a=
s
> time allows.

> I have seen previous discussion/patches on a built-in connection pooler. =
How
> does this scalability improvement, particularly idle connection improveme=
nts
> 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


As I understand it, the improvements made to GetSnapShotData() mean having =
higher connection count does not incur as much a penalty to performance as =
before.=20
I am not sure it solves the connection stablishment side of things, but I m=
ay be wrong.

Luis R. Weck=20