On Sat, Jul 05, 2008 at 10:38:14AM +0000, Ehl Le wrote:
> 
> I'm pretty annoyed now...  The last days I tried to set up slony to
> replicate the database on to slave from one master - that works very fine
> now.
> 
> But the problem is that slony requires from the slave to be able to
> connect to the master, something I don't want, since the slave is not
> entirely sealed, there are database-users on the slave-server, I do not
> want slony to store login-information in it's database on the slave nor do
> I want to allow access *from* a slave *to the master* (pg_hba) ...is that
> access really required?

Yes.  I expect you would have been less annoyed if you'd read the
documentation more carefully, because this is quite clearly noted there as a
requirement.  Sorry.

If you added an intermediate box that you could trust, you could use
logshipping to the box you don't trust.  That's one-way.

A