public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim Nasby <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: Ashutosh Bapat <[email protected]>
Cc: Andrey Borodin <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Konstantin Osipov <[email protected]>
Cc: Nikolay Samokhvalov <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Built-in Raft replication
Date: Wed, 23 Apr 2025 11:48:46 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKAnmm+QJnL_APyKhM3hjkOv9DXjWaqJxB2nFDuNH9JqVdTfXA@mail.gmail.com>
References: <Z_1Cq7JvabsFYjQo@ark>
	<CAKAnmmJxGHcQmzXqEQ-nppZjXyH7i5W_7Cz8JNMb2+6c5+D+og@mail.gmail.com>
	<CAM527d9+eGvdih1GxoPDJ2WYs6eitf39oNTxGxnCK1PgF=A8wg@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CAExHW5udz081Unx5qcLZ89DnR4cp6OhW0TCoco3+AEkGw480uQ@mail.gmail.com>
	<[email protected]>
	<CAExHW5tq8ShEfboFa52wDMWmyaW+6kX_6x8MZ-0TP65tOhJ1wQ@mail.gmail.com>
	<CAKAnmm+QJnL_APyKhM3hjkOv9DXjWaqJxB2nFDuNH9JqVdTfXA@mail.gmail.com>

On Apr 16, 2025, at 2:29 PM, Greg Sabino Mullane <[email protected]> wrote:
> 
> On Wed, Apr 16, 2025 at 2:18 AM Ashutosh Bapat <[email protected] <mailto:[email protected]>> wrote:
>> Users find it a waste of resources to deploy 3 big PostgreSQL instances just for HA where 2 suffice even if they deploy 3 lightweight DCS instances. Having only some of the nodes act as DCS and others purely PostgreSQL nodes will reduce waste of resources.
> 
> A big problem is that putting your DCS into Postgres means your whole system is now super-sensitive to IO/WAL-streaming issues, and a busy database doing database stuff is going to start affecting the DCS stuff.  With three lightweight DCS servers, you don't really need to worry about how stressed the database servers are. In that way, I feel etcd et al. are adhering to the unix philosophy of "do one thing, and do it well.”


… unless we added multiple WAL streams. That would allow for splitting WAL traffic across multiple devices as well as providing better support for configurations that don’t replicate the entire cluster. The current situation where delayed replication of a single table mandates retention of all the WAL for the entire cluster is less than ideal.

view thread (4+ messages)  latest in thread

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], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Built-in Raft replication
  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