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 1lHNrR-0004dA-FB
	for pgsql-admin@arkaria.postgresql.org; Wed, 03 Mar 2021 09:32:05 +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 1lHNrQ-0001yo-1C
	for pgsql-admin@arkaria.postgresql.org; Wed, 03 Mar 2021 09:32:04 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <vas@sibptus.ru>)
	id 1lHNrP-0001yb-Iw
	for pgsql-admin@lists.postgresql.org; Wed, 03 Mar 2021 09:32:03 +0000
Received: from admin.sibptus.ru ([2001:19f0:5001:21dc::10])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <vas@sibptus.ru>)
	id 1lHNrN-0003Xa-0q
	for pgsql-admin@lists.postgresql.org; Wed, 03 Mar 2021 09:32:03 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru;
	s=20181118; h=Message-ID:Subject:To:From:Date:In-Reply-To;
	bh=UrXx1mrNPn5WM2XnvA88Yj0PIjVYc2EYHXq7WG1JcHI=; b=lN9lYH73v4I76tGogQn/qmJTVG
	D3M7GxGXY84Dlb8PouCi6RhYM3/YxAJEIe/cTME/9IhEFy35dOhgJfH/PTuZ/164baA0e9fzwpmNC
	yZD+kbOlxiS/c8zswtvQP9PRzu8eZg/QnA6/kuXez5f+cTZTLVzNc6Box+wH/WRoP7zk=;
Received: from vas by admin.sibptus.ru with local (Exim 4.94 (FreeBSD))
	(envelope-from <vas@sibptus.ru>)
	id 1lHNrK-000LqE-6s
	for pgsql-admin@lists.postgresql.org; Wed, 03 Mar 2021 16:31:58 +0700
Date: Wed, 3 Mar 2021 16:31:58 +0700
From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: load balancer and connection pooling combined
Message-ID: <YD9XjqV5tNptwQVq@admin.sibptus.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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>
Precedence: bulk

Dear Colleagues,

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?

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