pg.ddx.io  pgsql-cluster-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Sabino Mullane <greg@endpoint.com>
To: Marcio Duarte <maethorin@gmail.com>
Cc: pgsql-cluster-hackers@postgresql.org
Subject: Re: Streaming replication for security
Date: Tue, 20 Dec 2016 10:33:17 -0500
Message-ID: <20161220153317.GB10656@localhost.localdomain> (raw)
In-Reply-To: <CA+Sm2LMPAKKi9xd7ns129+XPYYEZiX8P7-qXao5=zvDcOb0Apg@mail.gmail.com>
References: <CA+Sm2LMPAKKi9xd7ns129+XPYYEZiX8P7-qXao5=zvDcOb0Apg@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-cluster-hackers>

> 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 can 
come in to your database, via Postgres things like pg_hba.conf and good passwords, 
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 
WAL files from the master to the standby, by any secure means you want, 
iincluding an intermediary system. However, this can be hard/impossible 
for SaaS things like Heroku and RDS, which don't allow complete 
file-level access.

-- 
Greg Sabino Mullane greg@endpoint.com
End Point Corporation
PGP Key: 2529 DF6A B8F7 9407 E944  45B4 BC9B 9067 1496 4AC8

Attachments:

  signature.asc (application/pgp-signature, 162B) download

view thread (4+ messages)  latest in thread

Message-ID: <20161220153317.GB10656@localhost.localdomain>
Permalink:  ../20161220153317.GB10656@localhost.localdomain/
Also on:    postgresql.org/message-id/20161220153317.GB10656@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-cluster-hackers@postgresql.org
  Cc: greg@endpoint.com, maethorin@gmail.com
  Subject: Re: Streaming replication for security
  In-Reply-To: <20161220153317.GB10656@localhost.localdomain>
  References: <CA+Sm2LMPAKKi9xd7ns129+XPYYEZiX8P7-qXao5=zvDcOb0Apg@mail.gmail.com> <20161220153317.GB10656@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox