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-admin-owner+archive@lists.postgresql.org>)
	id 1lHOpx-0006Wi-Gk
	for pgsql-admin@arkaria.postgresql.org; Wed, 03 Mar 2021 10:34:37 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1lHOpw-0001Dn-7E
	for pgsql-admin@arkaria.postgresql.org; Wed, 03 Mar 2021 10:34:36 +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 <vas@sibptus.ru>)
	id 1lHOpv-0001Dg-6A
	for pgsql-admin@lists.postgresql.org; Wed, 03 Mar 2021 10:34:35 +0000
Received: from admin.sibptus.ru ([2001:19f0:5001:21dc::10])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <vas@sibptus.ru>)
	id 1lHOpr-0008Dg-Gt
	for pgsql-admin@lists.postgresql.org; Wed, 03 Mar 2021 10:34:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru;
	s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date;
	bh=egta2yVYiAhS7Obgchv5Je1sJxrKOh+ZWWOwo7p0wbk=; b=lyPST0WkX4P7A8/nnof+kuYs57
	5u1/UkgH5Fcdg+DpXUcnJtTa20+PrDOJuqR0Mbx1s7FNSkKPm2w9XKebFUfn8/jsU8biyGdBEs/zV
	hz6jUezH7m8rVuxFr2Gk00Ko1BmI1RRSiOGXO0l4HQqYBXTIxP7H4Fs4rLBuEaU7hXys=;
Received: from vas by admin.sibptus.ru with local (Exim 4.94 (FreeBSD))
	(envelope-from <vas@sibptus.ru>)
	id 1lHOpn-000MDV-Gp
	for pgsql-admin@lists.postgresql.org; Wed, 03 Mar 2021 17:34:27 +0700
Date: Wed, 3 Mar 2021 17:34:27 +0700
From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: Re: load balancer and connection pooling combined
Message-ID: <YD9mM7+LGQcMR2Vj@admin.sibptus.ru>
References: <YD9XjqV5tNptwQVq@admin.sibptus.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YD9XjqV5tNptwQVq@admin.sibptus.ru>
X-PGP-Key: http://admin.sibptus.ru/~vas/
X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9  3532 0DA4 F259 9B5E C634
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/YD9mM7%2BLGQcMR2Vj%40admin.sibptus.ru>
Precedence: bulk

Victor Sudakov wrote:
> 
> Based on your personal experience and industry best practices, what load
> balancer combined with connection pooler can you advise?
> 
> 1. I have good experience with pgpool, it's a great and robust
> connection pooler, but it cannot do load balancing and failover (or
> rather, it can do very rudimentary load balancing).
> 
> 2. I have limited experience with Haproxy, it's great for load balancing
> and failover, but it's not a connection pooler, and its pgsql-check is
> not good enough, I guess you have to use an external check.
> 
> Is there the "one thing to rule them all" that does all of the above and
> is well-tested and reliable?

If it could parse Patroni's REST API like Haproxy can, it would be even more perfect.

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet