The last place I worked used F5s for load balancing and Bucardo for replication. The F5s worked well enough, and I've become a huge fan of Bucardo. It has capab

The last place I worked used F5s for load balancing and Bucardo for replication. The F5s worked well enough, and I've become a huge fan of Bucardo. It has capabilities that I think blow Slony away. (Custom code, and pre-warmed slaves are two of the biggest differentiators.) The new job is doing something that could best be described as very primitive sharding (completely unnecessary, given the demonstrated loads compared to the levels of concurrency PostgreSQL can support with minimal tuning), without replication. I'm eliminating the former, and will eventually be adding some HA capabilities, and probably also bringing Bucardo in. I don't think SR is going to obsolete a connection pool any time soon -- you still need to direct traffic appropriately between master and slave(s). I've never used it, but I've consistently heard good things about pgBoucner as a connection pooler.