Add an user-friendly hint to the (in)famous "Failed to get pooled connection" error message
Add an user-friendly hint to the (in)famous "Failed to get pooled connection"
error message

At some point we should look at checking various related GUC parameters and
make sure that they have sane values. For example, user may increase
max_connections at the datanodes, but if she forgets to change the
max_pool_size to a more reasonable value, outgoing connections from a
coordinator or a datanode may not be enough, even though the target node can
accept incoming connections. Its generally hard to derive one value from
another because max_pool_size defines limit on outgoing connections from one
node, but max_connections defines the limit on incoming connections. But we can
still provide some useful hints if there is a gross mismatch of values based on
the number of datanodes and coordinators.

zeroae/postgres-xl,zeroae/postgres-xl,zeroae/postgres-xl,zeroae/postgres-xl,zeroae/postgres-xl