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 1oZvkr-0008Ld-43 for pgsql-admin@arkaria.postgresql.org; Sun, 18 Sep 2022 14:58:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oZvkp-0001Lx-Va for pgsql-admin@arkaria.postgresql.org; Sun, 18 Sep 2022 14:58:43 +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 1oZvkp-0001Ln-Jn for pgsql-admin@lists.postgresql.org; Sun, 18 Sep 2022 14:58:43 +0000 Received: from mail-ot1-x330.google.com ([2607:f8b0:4864:20::330]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oZvkn-00029M-8R for pgsql-admin@lists.postgresql.org; Sun, 18 Sep 2022 14:58:43 +0000 Received: by mail-ot1-x330.google.com with SMTP id w22-20020a056830061600b006546deda3f9so18214784oti.4 for ; Sun, 18 Sep 2022 07:58:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:from:content-language:to:user-agent:mime-version:date :message-id:from:to:cc:subject:date; bh=7W32iM6q9ViV2dOk/2xGNqC6inNZsIM43dTec5iWgdM=; b=iUMeF5dvGmG3wxZTgbhl5Mw5yEhVW1SSip238Mvgqzh9ZwMzIlS5977rJXLA+P2ciO +kHrumrU3+SyQkqu4eV2MY4xKExe7EdHXUHTc6W8IFgAft3KetxAtt9QOWq7eldVhm4y k7pp1T/It3BZgkSbexXXCdy2hReE01IlRSHra0Fkw6H36hGOcCDCSoU9cRkZYNRsiGGx 8whVEl0GKwygQDQJ+kLes/R6j6dmSP9oB8BDiJyxiOsLhrR2HhpSBVUeWFQ2Lvwla3nP Fkq5Cjt+o953mg+OOTcatGaZJL3w5QfTd1IpkzEVZgeeIK7ayoRE2GHh33eDtTcpospy 5E1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=subject:from:content-language:to:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date; bh=7W32iM6q9ViV2dOk/2xGNqC6inNZsIM43dTec5iWgdM=; b=8MQYz3WT7zmhV4NAVMU7Rl1852lh+YUHXH/naNraVjXDFws3vR+NE+L77Ygm5YCZ20 /0w1EypuX7EZVF/Ub7a7roHeQifAG7c3O9hrMHWgma3vaygBUJ3/v5Y6+fZBZYLVdcun vv9oZmFGMRW+6zHy5zlhFUUoGDiW9JHKEJ5gP7uf7PhEFmBxqudR2Ym9m2dnAdpLzo6M bCG+jHmS+A2wa42BKZzs9y3CFklYHzdj0okQ5u9cxAyRmaRzE45q7mX7qDNKskjrw644 ZYbMaLYjPB90bEeLmck3BAbwNhXB3LmZxCTTPwtoV4+fTOpEn8YvSqBwI5jMIEIo6Pn8 N3HQ== X-Gm-Message-State: ACrzQf0INQVK9+zcFIpP1fOqFaBKtU+qIPtI9SSoBNc1DK4erKj5qJn4 DJx2EHm4ppsPgY17XJSu/e9c4D5nleI= X-Google-Smtp-Source: AMsMyM45KygM/K7tmKw8eXEe3v1GO2Y8FswIXtdgp5mXi8rE9HYSjCiJA77iuDf5JR6plr/sTMf0nQ== X-Received: by 2002:a9d:71d3:0:b0:655:ba92:4a6 with SMTP id z19-20020a9d71d3000000b00655ba9204a6mr6332831otj.174.1663513119034; Sun, 18 Sep 2022 07:58:39 -0700 (PDT) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id l7-20020a4ab0c7000000b00475dc6c6f31sm3167121oon.45.2022.09.18.07.58.38 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 18 Sep 2022 07:58:38 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------bpsnWauDnKa3jUVqTYADAe1U" Message-ID: Date: Sun, 18 Sep 2022 09:58:37 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 To: "pgsql-admin@lists.postgresql.org" Content-Language: en-US From: Ron Subject: Postgresql version of SQL Server Availability Groups? 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. --------------bpsnWauDnKa3jUVqTYADAe1U Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Currently my customer has some very large stand-alone PostgreSQL 9.6 (will migrate next year to v13) databases, and they want to add HA. Specifically, they want a "cluster name" which points to a Primary database server's IP address, and and which automatically (presumably through through a heartbeat and quorum voting system) points to a Secondary database server's IP address if the Primary server goes down.  Both servers are in the same data center. (Replication would be handled by a standard PostgreSQL method.) This is *not* load balancing, but a purely HA solution. I looked at HAProxy, but it seems to be focused on load balancing, while the Patroni documentation does not seem to mention a cluster name. Am I missing something? -- Angular momentum makes the world go 'round. --------------bpsnWauDnKa3jUVqTYADAe1U Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Currently my customer has some very large stand-alone PostgreSQL 9.6 (will migrate next year to v13) databases, and they want to add HA.

Specifically, they want a "cluster name" which points to a Primary database server's IP address, and and which automatically (presumably through through a heartbeat and quorum voting system) points to a Secondary database server's IP address if the Primary server goes down.  Both servers are in the same data center.  (Replication would be handled by a standard PostgreSQL method.)

This is not load balancing, but a purely HA solution.

I looked at HAProxy, but it seems to be focused on load balancing, while the Patroni documentation does not seem to mention a cluster name.

Am I missing something?

--
Angular momentum makes the world go 'round.
--------------bpsnWauDnKa3jUVqTYADAe1U--