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@xxxxxxxx. 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-failover-when-master-crashes-tp5750442p5754606.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
