public inbox for [email protected]  

help / color / mirror / Atom feed

From: [email protected]
To: [email protected]
Subject: Re: Load balancing of write queries among health-checked nodes
Date: Tue, 08 Oct 2024 07:41:00 +0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANzqJaD5xa=5GSQ36R-c_i6kjSVtiA7S9LbCs_RaEBUE4STS9g@mail.gmail.com>
References: <[email protected]>
	<CANzqJaD5xa=5GSQ36R-c_i6kjSVtiA7S9LbCs_RaEBUE4STS9g@mail.gmail.com>

Among PostgreSQL instances there is only one master. But yes, each server may be considered master by the clients because it's Pgpool-II will redirect write queries to the actual master. Maybe it's even better to avoid this unnecessary traffic between servers and decide which Pgpool-II is in front of the master on the client side, but this is optional.

Dnia 8 października 2024 07:30:05 GMT+04:00, Ron Johnson <[email protected]> napisał/a:
>On Mon, Oct 7, 2024 at 11:04 PM <[email protected]> wrote:
>
>> Hello. I have a PostgreSQL high availability cluster with Pgpool-II, but I
>> don't use the virtual IP feature so my clients don't know which node to
>> send queries to. DNS round-robin is not a solution because it can't
>> distinguish between healthy and dead nodes.
>>
>> I thought about having a Pgpool-II instance on each client (client
>> Pgpool-II -> cluster Pgpool-II -> PostgreSQL), but AFAIK it can't
>> distribute write queries. I also know that libpq may have multiple nodes to
>> connect, but I need an advanced health check because a node may have
>> connectivity but be separated from the whole cluster so it must be
>> considered dead.
>>
>
>Isn't that multi-master clustering?
>

view thread (3+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Load balancing of write queries among health-checked nodes
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox