From: luis.roberto@siscobra.com.br
To: AJG <ayden@gera.co.nz>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Improving connection scalability: GetSnapshotData()
Date: Mon, 1 Mar 2021 09:49:47 -0300 (BRT)
Message-ID: <486489735.28495535.1614602987743.JavaMail.zimbra@siscobra.com.br> (raw)
In-Reply-To: <1614447658602-0.post@n3.nabble.com>
References: <20200301083601.ews6hz5dduc3w2se@alap3.anarazel.de>
<1614447658602-0.post@n3.nabble.com>
----- Mensagem original -----
> De: "AJG" <ayden@gera.co.nz>
> Para: "Pg Hackers" <pgsql-hackers@postgresql.org>
> Enviadas: Sábado, 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 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
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.
I am not sure it solves the connection stablishment side of things, but I may be wrong.
Luis R. Weck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: luis.roberto@siscobra.com.br, ayden@gera.co.nz
Subject: Re: Improving connection scalability: GetSnapshotData()
In-Reply-To: <486489735.28495535.1614602987743.JavaMail.zimbra@siscobra.com.br>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox