On Mon, Jan 02, 2017 at 07:43:04PM -0500, Andrei Tchijov wrote: > If we are > going to accept that we have to let Bucardo talk to Master, then we would > be better off, but use Bucardo “normal way”.
Well, perhaps. If Bucardo could be taught to do all its selects and, more importantly, its COPYs, from the replica, the extra overhead for Bucardo would be greatly reduced as it would be only touching the bucardo metadata tables on the master (plus the overhead of the triggers themselves, of course). What is the security concern about Bucardo talking directly to the master? I'm a paranoid type, but there are many layers of security on the RDS, the local OS, and the Postgres side that do a very good job of locking everyone else out. Hm....unless the concern is having a pseudo-superuser connect to the master, in which case I wonder if this new scheme would allow us to connect as a non-superuser, since we would not need to do any session_replication_role changes on the master. Maybe a change we should make anyway... /wild_speculation -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8
signature.asc
Description: PGP signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
