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: Wed, 8 May 2013 01:35:43 -0700 (PDT)
Message-ID: <1368002143827-5754684.post@n5.nabble.com> (raw)
In-Reply-To: <1367946428.1661.YahooMailNeo@web163503.mail.gq1.yahoo.com>
References: <515AEB4E.9010305@europecamions-interactive.com>
	<CALxYTP6sxtHSwfFk2C3n4cV59NNPcg2Po9R04SM8W9WTR1ThWw@mail.gmail.com>
	<1365617192.69337.YahooMailNeo@web163506.mail.gq1.yahoo.com>
	<20130410181656.GB32580@aart.rice.edu>
	<1367943441337-5754606.post@n5.nabble.com>
	<1367946428.1661.YahooMailNeo@web163503.mail.gq1.yahoo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Thanks for the response.  In terms of your suggestions:

1.  We already have stunnel installed on MachineA and MachineB, and it would
not be too difficult to install stunnel on MachineC either.  What I'm unsure
of is how to make MachineB a 'bridge' so the postgres target MachineC
appears as an end point to MachineA.  We just want to pass postgres rsync
through MachineB to MachineC and have commit notifications passed back to
MachineA (we're hoping to run postgres replication synchronously initially,
though if performance suffers too much we'll run async).

2. We're unable to stream directly to MachineB as it has its own postgres
database cluster which we don't want to write to.

For information, we're running Ubuntu 12.04 LTS and Postgres 9.2 on all
hosts.



--
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: <1368002143827-5754684.post@n5.nabble.com>
Permalink:  ../1368002143827-5754684.post@n5.nabble.com/
Also on:    postgresql.org/message-id/1368002143827-5754684.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: <1368002143827-5754684.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