On Wed, Oct 03, 2012 at 09:13:23AM -0700, David E. Wheeler wrote: ... >> Because you would be connected to the existing session, which >> would more than likely have session_replication_role = 'replica', >> which allows you to shoot yourself in the foot quite effectively >> indeed. > > Oh, I see. Hrm. I wonder if pgBouncer would reset such > things before assigning a connection to a new client.
Well there is server_reset_query, which you can define yourself, but such a reset would be a very, very bad idea as we *want* our session_replication_role to stay sticky! >> Would be cool if pgbouncer would look at the application_name >> and reject non-matching ones. > > I’ll go ask the pgBouncer folks. Not that it matters if > session pooling is kind of pointless. Well we are still aiming for txn-level, right? Which reminds me: if you are using pgbouncer, make sure you set all databases involved to server_side_prepare=false inside the bucardo.db table. -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8
pgpJoQp6qWT4n.pgp
Description: PGP signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
