Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cJMQB-0008Fd-Um for pgsql-cluster-hackers@arkaria.postgresql.org; Tue, 20 Dec 2016 15:33:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cJMQB-0002It-BG for pgsql-cluster-hackers@arkaria.postgresql.org; Tue, 20 Dec 2016 15:33:43 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cJMPv-0001zO-49 for pgsql-cluster-hackers@postgresql.org; Tue, 20 Dec 2016 15:33:27 +0000 Received: from mail.endcrypt.com ([2607:f0d0:1301:23::3]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cJMPo-0005Gd-FI for pgsql-cluster-hackers@postgresql.org; Tue, 20 Dec 2016 15:33:25 +0000 Received: from localhost.localdomain (107-145-65-119.res.bhn.net [107.145.65.119]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.endcrypt.com (Postfix) with ESMTPSA id 373E886E6F; Tue, 20 Dec 2016 15:33:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=endpoint.com; s=mail; t=1482247999; bh=SjWi5DFq5g8qRwFBRmYtyeZI+ia3KsBb3m2pNwHpi6E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KkNtoyCB8M6+c2bNqaCE6h7j6btnGgYkMaSME4N3D2eVyo8RPpUe6W1BTPuECiJTD Q21Y5Y2EFn4dsr/CgfLlLWRaMeXweOGwPyXTRZu7fagdchh/l7prQRm1jBEexqPUbi tY3ptKbtYzu9ZyYPowjsDNr2hnGhzxZ/VqvtkZUIuyV0rt5IvHD5f/9WHy1lR0tT1s Sk+OZu4w5tKihNjLNxZ7+tKzFLpVD/74at8ynL+FPk2MnCSHEndsFt2UOlKzaB98DN IZPwd06ic5yhCPI4UAUwvpU8fYv6XnGqycOzvGCZq1cZ4FVMUX/DH51x7eTtvdPuwu gqUa9lIXK+RDQ== Date: Tue, 20 Dec 2016 10:33:17 -0500 From: Greg Sabino Mullane To: Marcio Duarte Cc: pgsql-cluster-hackers@postgresql.org Subject: Re: Streaming replication for security Message-ID: <20161220153317.GB10656@localhost.localdomain> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="hHWLQfXTYDoKhP50" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.gtsm.com/Greg_Sabino_Mullane.key.html User-Agent: Mutt/1.6.1 (2016-04-27) 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 --hHWLQfXTYDoKhP50 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > case, I will need to expose the internal database server to the Web via > TCP, right? Technically, yes, but you still have pretty fine-grained control over who c= an=20 come in to your database, via Postgres things like pg_hba.conf and good pas= swords,=20 as well as OS-level things like iptables and port knocking. > If so, there is a way to make the master send the data to standby? You could certainly use traditional file-based log shipping to move the=20 WAL files from the master to the standby, by any secure means you want,=20 iincluding an intermediary system. However, this can be hard/impossible=20 for SaaS things like Heroku and RDS, which don't allow complete=20 file-level access. --=20 Greg Sabino Mullane greg@endpoint.com End Point Corporation PGP Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8 --hHWLQfXTYDoKhP50 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAlhZTz0ACgkQvJuQZxSWSsgXEQCgjz4KJzGWYMq7iBN8uwnt35Y0 FvIAoNTa13LzFg0gTSVvusb6l3s0cKvo =husN -----END PGP SIGNATURE----- --hHWLQfXTYDoKhP50--