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.94.2) (envelope-from ) id 1to0PP-004iUz-6x for pgsql-admin@arkaria.postgresql.org; Fri, 28 Feb 2025 13:28:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1to0PQ-006Blu-AC for pgsql-admin@arkaria.postgresql.org; Fri, 28 Feb 2025 13:28:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1to0PP-006Bli-VM for pgsql-admin@lists.postgresql.org; Fri, 28 Feb 2025 13:28:06 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1to0PK-000BAv-1w for pgsql-admin@lists.postgresql.org; Fri, 28 Feb 2025 13:28:06 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 3967BE2115; Fri, 28 Feb 2025 13:28:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elevated-dev.com; s=easymail; t=1740749281; bh=iGzRJS4rJpW9cwXNZ/dypFD9EtK1SvshhfmKmE26qPM=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=4RufhIhxsewo+F1YZBrMPQKbl2TP5bZBS8nXHF6AB7K81NilRh+TLZr5K4pQug7L+ RfRMjU9/dnEwNufowDItyaW1LSillJIhGd1rjzseLRGC7+sUqdxigHFIBcKRK2k5rE P2p3w9VPzR/2NNT3VyO3wQc3nEqHMeSZhKbolFSgJJpY/FlOno4EgTKXKHcdEFN3d4 iNsS5lpxndZJs/7EcQhxfxShmcNtBk8KSVUbaw70R3bpNWttehbdLqfHdFIssxMFnf LQBa9v4AdDPamNg8RkenUkcRvKW2gmXRdLjsyC4eemINVLF7wgKiMm+Feq8E/cARiz rU7DMPGoEv+Tg== X-Virus-Scanned: Debian amavisd-new at emo08-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo08-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zwC8u0ippZA8; Fri, 28 Feb 2025 13:28:00 +0000 (UTC) Received: from smtpclient.apple (unknown [165.140.184.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 9970BE1F26; Fri, 28 Feb 2025 13:28:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elevated-dev.com; s=easymail; t=1740749280; bh=iGzRJS4rJpW9cwXNZ/dypFD9EtK1SvshhfmKmE26qPM=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=Js3Flz4uikwI72k2c+qhgfd1xQ3dFd7rYkPw0QBZ/cSd80GjsIGD03lHdULVS7fES Zk5E7taOtluF53AbKCpUSwl8k1rdFIWvm/nFilXALC/lZ6M/aY9QNzNWarV0OT7KHu 3w2I4dbR1oO1v4dxwn18SID6JAIn/xDhl35m1+CyNRAkhT8CKtL0fVEBK5ffmTqeIp K2qbkFlMXb7YkFPMfWJmAbxdbaj+iGMANLMUQd/Rzlbo7E20G8Tjc8+T82SvI43w5R 39c12lQCHuj4SCD+Tbw27vdhPNVWI373PBT8d/PKaXt6FjGxO9lyLKf9cUhs9fPSA3 YRmym10aU3FRA== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\)) Subject: Re: Multi-MASTER across different locations From: Scott Ribe In-Reply-To: Date: Fri, 28 Feb 2025 06:27:50 -0700 Cc: pgsql-admin@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <47328915-B768-42EC-A55B-C1CD130A487C@elevated-dev.com> References: To: ek ek X-Mailer: Apple Mail (2.3826.400.131.1.6) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Sure, the solutions can run across different data centers. As always, = you will have to understand all cases of possible update conflicts and = deal with them. -- Scott Ribe scott_ribe@elevated-dev.com https://www.linkedin.com/in/scottribe/ > On Feb 28, 2025, at 12:22=E2=80=AFAM, ek ek = wrote: >=20 >=20 > ---------- Forwarded message --------- > From: ek ek > Date: Fri, Feb 28, 2025, 09:21 > Subject: Multi-MASTER across different locations > To: >=20 >=20 > Hello everyone, > Can two different master servers (multi-master) run as a cluster = across different data centers in PostgreSQL? I've seen some solutions, = but I'm not sure if they work correctly. Could you share your = experiences?