Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cqQqc-0001BP-Jw for pgsql-cluster-hackers@arkaria.postgresql.org; Tue, 21 Mar 2017 20:57:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cqQqc-0004Ih-2O for pgsql-cluster-hackers@arkaria.postgresql.org; Tue, 21 Mar 2017 20:57:42 +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 1cqQqK-0003nb-U0 for pgsql-cluster-hackers@postgresql.org; Tue, 21 Mar 2017 20:57:24 +0000 Received: from mail.endcrypt.com ([2607:f0d0:1301:23::3]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cqQqD-0002gu-AK for pgsql-cluster-hackers@postgresql.org; Tue, 21 Mar 2017 20:57:24 +0000 Received: from localhost.localdomain (pool-74-103-176-137.phlapa.fios.verizon.net [74.103.176.137]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.endcrypt.com (Postfix) with ESMTPSA id E3C5487816; Tue, 21 Mar 2017 20:57:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=endpoint.com; s=mail; t=1490129833; bh=vyazyPIwoHqw9/MJb0AqykeHWqQY69z3AJWa+jY6lNw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ppAjXM24m3u3vQZvEYhdb0qS6/lgys70UeGG2oQi+8SvBAI4zMCN2xV7qpNZMfr3S jC3p3Eu0Z8ogWwxekwWjzvef/nXBA+xvFdkjd2N7BHTKn60XRKcW1vcYLDG4UfokJP wZqtgUnqEO9XsksB7EHi7aorgJdDKq+FhQNcrXeudur/qiSrsO7423DiaOmQiqf68E vkMWlMFuOmqJjDbd32ISTLba0tBopvT4k8lM+5p2GMdcyQJVD059eoWVDKKF1GWF01 Uj0V/uglQ/qNJypUXCnnYGjULc0HJgcIAIGpqAGMAG79psf/sDQEUMb3B4PJx76VP/ dSL4jOnxE2U1A== Date: Tue, 21 Mar 2017 16:57:10 -0400 From: Greg Sabino Mullane To: DEV_OPS Cc: pgsql-cluster-hackers@postgresql.org Subject: Re: Replication over RDMA with Infiniband or RoCE Message-ID: <20170321205710.GD14887@localhost.localdomain> References: <20170319184748.GT14887@localhost.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="Km2V3aJx5eFEhJmw" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.gtsm.com/Greg_Sabino_Mullane.key.html User-Agent: Mutt/1.7.1 (2016-10-04) X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-cluster-hackers Precedence: bulk Sender: pgsql-cluster-hackers-owner@postgresql.org --Km2V3aJx5eFEhJmw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > Yes, we are going to implement this over Postgres' streaming replication > system, > the usecase is DR, eg: the sync between two datacenter in same city, > there had FC link, (Now FC could be used to extend IB network, so we are > going to implement the native RDMA replication for low latency purpose > for that case-- it is very import for some critical system, also, this > replication is preferred base on Postgres' stream replication ) =2E.. Well, I think the starting point should be, why is streaming replication=20 not preferred? It's very fast and very robust. > 2.) the IB based replication system will work with current IP based > replication system, it mean that, in a replication system, maybe had IB > replication, and also had IP replication, the case1 is: NodeA to NodeB > to NodeC, NodeA -IB->NodeB --IP-->NodeC ; means, NodeA to NodeB could > be IB base replication, it provide low latency ; and NodeB to NodeC > it is based on IP, it's orig IP based replication system ; the case2 > is: NodeA--IB-->NodeB, NodeA--IP-->NodeC ; means NodeA to NodeB is IB > replication; and NodeA to NodeC is IP based replication, >=20 > 3.) it will support sync replication and async replication ; also > support phy replication and logical replication . =2E.. Honestly, that sounds fairly complex, for not a lot of gain, but I don't=20 know that I am competely understanding your proposal. This is a very=20 low-activity mailing list - what I would recommend at this point is writing= =20 up a concise statement about why you need this and run it up the flagpole= =20 to pgsql-hackers@postgresql.org. I promise you will get more of a response= =20 there, for better or for worse. :) --=20 Greg Sabino Mullane greg@endpoint.com End Point Corporation PGP Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8 --Km2V3aJx5eFEhJmw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAljRk6UACgkQvJuQZxSWSsgt8ACg+wUaRs3h0iZi3J07qI2eGWHZ 9A4AoLQ4bxKtVfA+xcwhsyhVXJtbFy+5 =pC4/ -----END PGP SIGNATURE----- --Km2V3aJx5eFEhJmw--