Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wR9Pj-0028m6-34 for pgsql-general@arkaria.postgresql.org; Sun, 24 May 2026 14:02:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wR9Oh-00GxoC-24 for pgsql-general@arkaria.postgresql.org; Sun, 24 May 2026 14:01:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wR9Oh-00Gxo2-0n for pgsql-general@lists.postgresql.org; Sun, 24 May 2026 14:01:44 +0000 Received: from mx2.edn2.eu ([2a01:4f9:c01f:c001::1]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wR9Oe-00000000Z35-37aM for pgsql-general@lists.postgresql.org; Sun, 24 May 2026 14:01:43 +0000 Received: from smtpclient.apple (p200300fb4f36b201083464396f097527.dip0.t-ipconnect.de [IPv6:2003:fb:4f36:b201:834:6439:6f09:7527]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.edn2.eu (Postfix) with ESMTPSA id 4gNgfb5MQSz12QR for ; Sun, 24 May 2026 16:01:27 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellael.org; s=dkim; t=1779631287; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=brn80mnfMTb/rsNjFejTk4WGYLX6CuqqVWAsFkjPNWI=; b=KOfDMX+IaJqTXK0TBx/fX4InRv+Wi3k91y7BgjUuVggeVA6SwTApsHPOi1OIYoZ6k1k1wc AdcVldKDVLc7PU3SuA6VdRToLlp4m10ds1rRV2xYKuF0K0n+zW4vL383KHUaouJRKVa6/J 5fgfuqiIReEX/jpzp8YxqJ/n0QPQWvBXrwVrfxDC29ro0uEkbPaM5oOgRfZVBXUX+SDuTT 6x5eh/huGn0IZw5HkOFOnch8DeEzSLJzFqYNeS1J/REZMZM2QDDQJMyMEHll6CXG7Yqf4C 7KLwW6pyLmrtk0DBgvml2rRrysULdWIkF8G8cqVqXQO5DKtpuv29NWoJE6e/1A== From: Michael Grimm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\)) Subject: Re: Can logical replication be a solution to my current MariaDB/Galera setup? Date: Sun, 24 May 2026 16:01:17 +0200 References: To: pgsql-general@lists.postgresql.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3864.600.51.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk shammat@gmx.net wrote: > Am 22.05.26 um 15:18 schrieb Michael Grimm: >> I have never run a postgres server before, but I do run a mariadb >> galera cluster [1] for storing emails by an IMAP server [2]. >> Distribution and failover is dealt by haproxy [3]. >=20 > For such a system I don't see the need for a multi-master setup = (neither > with Postgres nor with MariaDB). What I didn't mention in my mail is: incoming mails at all three mail = servers become stored into each user's mailbox at the server they = arrive (LMTP). In this scenario multi-master is handy. But see below. > For high availability you don't need multi-master. A standard > streaming replication with a failover mechanism is completely enough > in my opinion. Thanks for this hint w.r.t. streaming replication. I have made some research about this kind of cluster and come to the = conclusion that streaming replication plus repmgr [1] will meet my = expectations. BUT: I will need to configure haproxy to route all IMAP and LMTP traffic = to the "current" master, only.=20 I am hoping that this can be achieved by a customised health check plus = routing, but I have never done that before, though. Thanks and regards, Michael [1] available in the FreeBSD ports collection=