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 1oa28r-00015H-BO for pgsql-admin@arkaria.postgresql.org; Sun, 18 Sep 2022 21:47:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oa28q-0006ht-4X for pgsql-admin@arkaria.postgresql.org; Sun, 18 Sep 2022 21:47:56 +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 ) id 1oa28p-0006hj-OB for pgsql-admin@lists.postgresql.org; Sun, 18 Sep 2022 21:47:55 +0000 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oa28j-0005Fj-2w for pgsql-admin@lists.postgresql.org; Sun, 18 Sep 2022 21:47:54 +0000 Received: by mail-oi1-x233.google.com with SMTP id w125so12510626oig.3 for ; Sun, 18 Sep 2022 14:47:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date; bh=h5PPMy+pLCwNXQDuifoa0Cd8TGhHv1FMwmPckEdHjKw=; b=CWxPp8B9Y2eW/AZWAmRUuDlDfCwPL75vU990vZFlDpCZRlpSwKSHWJ/CtBxNujGDTe GOlwbXtUUF/1Y7ucKWYqp0001EPr0Uo+b3bIEeg9SR38XHzEWViqhL99GI5nFQLgKbBc wWnYeCNBNN9Vu1yzwQeNw1bVWX0a3qJ1XDbHIUYs9C+/K4cH+7jgb2AUbbELdhO6MZmB HThgWuPrbUFizKHqSRO5+B+ExE3wS+9xDZ+c50gIZa6xNU1MpKWdbvxTpjKLFXuY7475 OJWeyv1eyMhEntfFvpcrdkvmUYYjynFcLokdN4nIFDqPAz5cebjs6odMXBEiPoXqg9kW v9PQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date; bh=h5PPMy+pLCwNXQDuifoa0Cd8TGhHv1FMwmPckEdHjKw=; b=bs9HMzN/VnggyIm4v7SiICFqczX/tD7MC6zNzZkoaAqEWCKufXriQV99Su+ESKyPmG /DB1UZTooC6PDYaJIqnyELIyoB/i8+jZURLqP5HQkr55dD0kkgqhIuHBM35YMPRc7Y4u 77HdfD6+cn8pPmfmdQcwnMVrwZkpNfdEE95xCgLCZ3gzWDDP+RgmDX/y6Bio95uia51U il8iczW+9yFrK9yuuap5UITS7RU9v3eLuiUXS4chI3iRMo/Ui24ZgmWhmko2bBLD/lJp hCUYGqagnf4Tbu3P1Nq4kker8OAMw0tcM7VcNwwN/XUVjW0wrXmJYDBE87DvY8YFV+xU H+aA== X-Gm-Message-State: ACgBeo3NrSJ9UpdUxY0UzMRPmLj94TSExoCgtSxhzPxM7j4Dzq/BAA8v zwnjQ0bQkJl2FMtQxwehdK7tlDlVZXg= X-Google-Smtp-Source: AA6agR6Ip606GNco9d0jCawAD2SAK8uDs9fg0mkOPQPpI/PjLpdFyQZThltC5CHmtVRq+yKtuh88Hw== X-Received: by 2002:a05:6808:1719:b0:34d:444a:58c0 with SMTP id bc25-20020a056808171900b0034d444a58c0mr10518048oib.11.1663537668045; Sun, 18 Sep 2022 14:47:48 -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 z9-20020a4ab889000000b00475dad5d64fsm3564368ooo.5.2022.09.18.14.47.47 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 18 Sep 2022 14:47:47 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------8QU8uivhLXzXJxKqktjCarQY" Message-ID: Date: Sun, 18 Sep 2022 16:47:46 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: Postgresql version of SQL Server Availability Groups? Content-Language: en-US To: "pgsql-admin@lists.postgresql.org" References: From: Ron 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. --------------8QU8uivhLXzXJxKqktjCarQY Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Quite possibly. Thank you. On 9/18/22 14:23, Licio Matos wrote: > Hi Ron! > > Look if pgpool can handle your request > > https://www.pgpool.net/docs/37/en/html/example-cluster.html > > > Em dom., 18 de set. de 2022 às 11:58, Ron escreveu: > > 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. > > -- > Licio Matos -- Angular momentum makes the world go 'round. --------------8QU8uivhLXzXJxKqktjCarQY Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Quite possibly.

Thank you.

On 9/18/22 14:23, Licio Matos wrote:
Hi Ron!

Look if pgpool can handle your request


Em dom., 18 de set. de 2022 às 11:58, Ron <ronljohnsonjr@gmail.com> escreveu:
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.
--
Licio Matos

--
Angular momentum makes the world go 'round.
--------------8QU8uivhLXzXJxKqktjCarQY--