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 ) id 1pjgu7-0002Dq-6s for pgsql-general@arkaria.postgresql.org; Tue, 04 Apr 2023 13:40:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pjgu5-0004Zj-Ar for pgsql-general@arkaria.postgresql.org; Tue, 04 Apr 2023 13:40:53 +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 ) id 1pjgu4-0004Za-V9 for pgsql-general@lists.postgresql.org; Tue, 04 Apr 2023 13:40:53 +0000 Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pjgu2-000qBR-5r for pgsql-general@lists.postgresql.org; Tue, 04 Apr 2023 13:40:52 +0000 Received: by mail-wm1-x32c.google.com with SMTP id l10-20020a05600c1d0a00b003f04bd3691eso5201563wms.5 for ; Tue, 04 Apr 2023 06:40:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680615646; h=in-reply-to:from:cc:references:to:subject:user-agent:mime-version :date:message-id:from:to:cc:subject:date:message-id:reply-to; bh=oHg74vKtlZbOEj0/kSt0TgAziUkAvBqSUzEfWWj3MZo=; b=oTD2VNb29weEC/5rD/SHrxtG1Oid3vNwM6A7B+q3HIWKR1l7At5hWUESaFHtdZWstt UWIolyjicT80ZXnqeplq8Cgy2dAv0oMBqsOdh2HZYxqgrGrRg3Oy89bHJ1Pj8CnJdq5x P9IgADisOGz5Aq/WMd+iUN2bLQ5EHqlKi5MXoWtbnt59IoOpmJ9w0eD2vy4GSCXWiZ0y +nl4D6kXrVf3cT0ZWk4fyZJHkmZNPB4CZCO+FWfW77NEHec62/xXMpAOV9Hvo+zJhL7G HCU2EuLj7F3uD5AXnAXeQA22DgorhkPKbV9O6+NLMdQwjAEYDAwC2cCSRDECyFICwtsH vG9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680615646; h=in-reply-to:from:cc:references:to:subject:user-agent:mime-version :date:message-id:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=oHg74vKtlZbOEj0/kSt0TgAziUkAvBqSUzEfWWj3MZo=; b=m2KkzudQdv3eztsr0K9pt39TjGHclS3u4qFqEwYqnAcbmwQUJ5nesw1J7yCTTef34z ftbNaWGpbZAFtWiFMk4VMg0e0dGaTvihLXvX83p8itfeHDzkzLEc7Wjocbt4MeUh8cqC 6+uOAP80Fr9+6/4GI8+3fY0Armbx95M17j90/7GNjday7IxEbvCgkVp8/DzJtpRooBA/ on6rk6cb6h8fI5Ke5ObeNy1CMxdtGnby1XOKQmFShLKDWyb+vd60/elnebN04t4enDc+ l738pLFBJhgm+0QZZR8Q77nOQgvhEV5QfmJYDgXm2XnECPal4NJMD27VFDa2JZC8nmaM 0spQ== X-Gm-Message-State: AAQBX9f9pdCT04O+Awk0GqStUoU7u7SSJnr7LrNxor45Zq1EheI65zKh kvb3qg8ZKMD+oO2QOsUf1/M= X-Google-Smtp-Source: AKy350ZsrWQot1RUcssXPVTDi+USk8CiyCFkfSWBBR7+TsR1y7ceB8HOq5L6QQbZAhyxjeou5xGZFg== X-Received: by 2002:a05:600c:2312:b0:3ef:6396:d9c8 with SMTP id 18-20020a05600c231200b003ef6396d9c8mr2073507wmo.5.1680615646154; Tue, 04 Apr 2023 06:40:46 -0700 (PDT) Received: from [192.168.1.6] (BSN-95-228-180.static.siol.net. [193.95.228.180]) by smtp.gmail.com with ESMTPSA id 5-20020a05600c228500b003e91b9a92c9sm15208076wmf.24.2023.04.04.06.40.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 Apr 2023 06:40:45 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------ub0i0IcIVJn0gtlShiT42qXL" Message-ID: <3a4d8c1c-c703-4eb3-a442-cb9f40796b2d@gmail.com> Date: Tue, 4 Apr 2023 15:40:44 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: Patroni vs pgpool II To: Inzamam Shafiq References: Cc: "pgsql-general@lists.postgresql.org" From: cen In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------ub0i0IcIVJn0gtlShiT42qXL Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit > Can someone please suggest what is one (Patroni vs PGPool II) is best > for achieving HA/Auto failover, Load balancing for DB servers. Along > with this, can you please share the company/client names using these > tools for large PG databases? Having used pgpool in multiple production deployments I swore to never use it again, ever. The first reason is that you need a doctorate degree to try to understand how it actually works, what the pcp commands do in each scenario and how to correctly write the failover scripts. It is basically a daemon glued together with scripts for which you are entirely responsible for. Any small mistake in failover scripts and cluster entersĀ  a broken state. Even once you have it set up as it should, yes, it will fail over correctly but it won't autoheal without manual intervention. You also often end up in weird situation when backends are up, pgpool reports down and similar scenarios and then you need to run the precise sequence of pcp commands to recover or destroy your whole cluster in the process if you mistype. I haven't used patroni yet but it surely can't be worse. Best regards, cen --------------ub0i0IcIVJn0gtlShiT42qXL Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit


Can someone please suggest what is one (Patroni vs PGPool II) is best for achieving HA/Auto failover, Load balancing for DB servers. Along with this, can you please share the company/client names using these tools for large PG databases?

Having used pgpool in multiple production deployments I swore to never use it again, ever.

The first reason is that you need a doctorate degree to try to understand how it actually works, what the pcp commands do in each scenario and how to correctly write the failover scripts.

It is basically a daemon glued together with scripts for which you are entirely responsible for. Any small mistake in failover scripts and cluster entersĀ  a broken state.

Even once you have it set up as it should, yes, it will fail over correctly but it won't autoheal without manual intervention.

You also often end up in weird situation when backends are up, pgpool reports down and similar scenarios and then you need to run the precise sequence of pcp commands to recover

or destroy your whole cluster in the process if you mistype.


I haven't used patroni yet but it surely can't be worse.


Best regards, cen

--------------ub0i0IcIVJn0gtlShiT42qXL--