Sure. It's all just code. It's not particularly a question of efficiency, I'm sure it could be made equally efficient. But "simpler" code-wise would be not having two implementations, or not having one that is designed to try to keep up with spike demands. The question for this group was really around PostgreSQL performance regarding the impact of idle connections. If there is a pool of 20 connections, and half of them are idle, what is the impact performance-wise of the idle connections on the active connections?