From: AJG <ayden@gera.co.nz>
To: pgsql-hackers@postgresql.org
Subject: Re: Improving connection scalability: GetSnapshotData()
Date: Sat, 27 Feb 2021 10:40:58 -0700 (MST)
Message-ID: <1614447658602-0.post@n3.nabble.com> (raw)
In-Reply-To: <20200301083601.ews6hz5dduc3w2se@alap3.anarazel.de>
References: <20200301083601.ews6hz5dduc3w2se@alap3.anarazel.de>
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
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: ayden@gera.co.nz
Subject: Re: Improving connection scalability: GetSnapshotData()
In-Reply-To: <1614447658602-0.post@n3.nabble.com>
* 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