We might just include pgbouncer in our default hosted offering.
@Anurag Goel: that would be “very lit”
@Anurag Goel: Are you envisioning exposing config options? We use https://github.com/awslabs/pgbouncer-rr-patch and would like that supported, if possible.
@Braden Sidoti: cc @Adrian Duong
@Braden Sidoti: It doesn't seem this is just a configuration on pgbouncer but a patch. We probably wouldn't be supporting this out of the box. We could have a template for this though.
@Adrian Duong: Yes, that's correct. Our setup uses the patch and changes a bunch of the standard config that we can't do with heroku's connection pooler. If we can't do the patch, we won't have a use for the standard config, though.
Our bouncer is public facing, so unfortunately I don't think we can move it off AWS until we can open arbitrary TCP ports.