Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ejQiN-0004OB-7A for pgsql-admin@arkaria.postgresql.org; Wed, 07 Feb 2018 14:28:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ejQiL-0001ac-CM for pgsql-admin@arkaria.postgresql.org; Wed, 07 Feb 2018 14:28:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ejQiL-0001aO-1f; Wed, 07 Feb 2018 14:28:45 +0000 Received: from mail-ua0-x241.google.com ([2607:f8b0:400c:c08::241]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ejQiG-0001pm-IH; Wed, 07 Feb 2018 14:28:44 +0000 Received: by mail-ua0-x241.google.com with SMTP id j23so639703uak.13; Wed, 07 Feb 2018 06:28:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=ueYz0vMMmh1L1mwxoQ3cQZKozmv+jbQrB7x/StaFXWA=; b=POyGr3pbha2ytStYGgLHo7DMNA6AiUMySzCNPlsCHiiZBT27BRyQMPgpCLJMb4+Ne8 OyAOegktgEstBqLtZaWDx8L70DJbW2FmcD/TNQy4PmqVikCz7++IM+VpM/g5LzOgck1p gUddgqRVseLUNrAWObAEBNkn3uW80LbVepwVAH390gvvuAWYB/GaQvtOJfzeUX6+US6K 1r9xowY6WYupB5KyuxCTIKUys0PVELz9W3v19aJoQeGwPeWbeoFVUyLoJaCO+HxLAxOl j7jE5fIDpGDlJuLebao28p5XCS6X6cuT+GJY30qsQC9wC2GWkQVenr0xQxrPOizzpqST EtGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=ueYz0vMMmh1L1mwxoQ3cQZKozmv+jbQrB7x/StaFXWA=; b=MpZEa+UOMTFxTSab09o5MWmihahHhvpn86nhKbYG2dxU2pg2tT23ZPYolGSZYB2N6/ l+VLtc+yuhfLdLs4DJUuVuV8s3/8WNQqF4iOBfN5LVgKIkKgT9YvQZ9Z6Upfr45KF/UZ XJOd9ySlx2SvbzWIh4Ft4BkUpmjtcctZ5bbMtvKsyqBM9PKgaaCsjLvvzarTEVFZv4Ac +mDsaa0yVrpniAIFMsSEr6ovVlW/3y7zuv8qLLfZlL7pXRu40TXbUdMhLBadSO+Z8Xcc XhooNmNdYfQ5pEVqG3d1HX/Boghvql4OOoxtAgcWhVFIzrwAGaTokfhuCDGCWqzjgn0+ XBvw== X-Gm-Message-State: APf1xPBhde75vYeZSRLmz++r2CsGU6GYuTE8uDo5my6AaVm9ZEFwk+xk zAVBKC9Xkp1MxPfGBUBJTJbIDA== X-Google-Smtp-Source: AH8x226lYefA00aux7X+bw+uMPZcm0sLrcmu3VZ6B8S9ZHWkryGBvsUr/Zx71zhIiZ8XZnfv6cYpig== X-Received: by 10.176.24.161 with SMTP id t33mr5586153uag.118.1518013718436; Wed, 07 Feb 2018 06:28:38 -0800 (PST) Received: from irylachi ([200.55.161.75]) by smtp.gmail.com with ESMTPSA id i74sm369709vke.18.2018.02.07.06.28.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 07 Feb 2018 06:28:37 -0800 (PST) From: "Lazaro Garcia" To: "'Stephen Frost'" , "'Dhandapani Shanmugam'" Cc: "'pgsql-admin'" , References: <20180206111200.GH2416@tamriel.snowman.net> In-Reply-To: <20180206111200.GH2416@tamriel.snowman.net> Subject: RE: PostgreSQL Active-Active Date: Wed, 7 Feb 2018 09:28:34 -0500 Message-ID: <002901d3a01f$f0fc6720$d2f53560$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQGRFeJFSc0DS8VKpcgc/HJBlB0NYAJTLsjOpAt6W+A= Content-Language: es-mx List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Do you have any tutorial about patroni + ha-proxy with postgresql (what about load balancing with this setup?) Regards. -----Mensaje original----- De: Stephen Frost [mailto:sfrost@snowman.net] Enviado el: martes, 6 de febrero de 2018 06:12 a. m. Para: Dhandapani Shanmugam CC: pgsql-admin; pgsql-general@postgresql.org Asunto: Re: PostgreSQL Active-Active Greetings, * Dhandapani Shanmugam (postgresql95@gmail.com) wrote: > Do we have active-active setup in postgreSQL, like we have in oracle RAC?. > Sorry if this question has been addressed already. What will be best > open source HA for postgresql with zero RTO and RPO. What you're probably looking for is a 3 (or more) node setup with patroni, etcd, and synchronous replication. Note that this will be a shared-nothing architecture, avoiding the risk that something bad happens with the storage system but requiring that the data be replicated multiple times. Using synchronous replication means that you have to have the nodes all close to each other, of course, but meets the zero RPO. Zero RTO is just silly, but with patroni and haproxy you can detect and failover pretty darn fast. Thanks! Stephen