pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: handsfree <luke.hansbury@redwood.com>
To: pgsql-admin@postgresql.org
Subject: Re: [SQL] Encrypting PGBouncer to Postgres DB connections
Date: Tue, 7 May 2013 09:17:21 -0700 (PDT)
Message-ID: <1367943441337-5754606.post@n5.nabble.com> (raw)
In-Reply-To: <20130410181656.GB32580@aart.rice.edu>
References: <515AEB4E.9010305@europecamions-interactive.com>
	<CALxYTP6sxtHSwfFk2C3n4cV59NNPcg2Po9R04SM8W9WTR1ThWw@mail.gmail.com>
	<1365617192.69337.YahooMailNeo@web163506.mail.gq1.yahoo.com>
	<20130410181656.GB32580@aart.rice.edu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

We're looking to use streaming replication to a target via a secondary host
using stunnel.  I'd love to hear how you were able to achieve this,
ktm@rice.edu.

Effectively we're looking to have the database on our customer's site (let's
call that MachineA) replicate to our backend postgres target in the cloud
(let's call that MachineC).  However, MachineA has no direct communication
with MachineC, in fact, it should never be allowed to communicate with it. 
We have another server that provides various services to the client MachineA
that is based in our home datacenter (let's call that MachineB) which we
would like to use as a 'staging' machine for the replication to the database
replication target.  Is this possible to achieve using stunnel (and
pgbouncer?) alone?  

At no point can this traffic go 'in the clear', for obvious reasons ;)

Any pointers or assistance help gratefully received!  Thanks



--
View this message in context: http://postgresql.1045698.n5.nabble.com/Hot-standby-with-streaming-replication-under-PgSQL-9-1-x-fai...
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (9+ messages)  latest in thread

Message-ID: <1367943441337-5754606.post@n5.nabble.com>
Permalink:  ../1367943441337-5754606.post@n5.nabble.com/
Also on:    postgresql.org/message-id/1367943441337-5754606.post@n5.nabble.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: luke.hansbury@redwood.com, pgsql-admin@postgresql.org
  Subject: Re: [SQL] Encrypting PGBouncer to Postgres DB connections
  In-Reply-To: <1367943441337-5754606.post@n5.nabble.com>

* 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