Map "pool" to "max_connections"

[nirvdrum]

This is likely my fault, but I assumed that sequel-rails remapped most of ActiveRecord's parameters in database.yml to Sequel's. As it turns out, Sequel uses a "max_connections" parameter, not "pool" to configure the pool size. The result is I've been running with a pool size of 4 connections in production for an embarrassingly long time. Fixing this resolved several issues for us.

Since the configuration mapper seems to already handle other attribute mappings, perhaps extending it handle the "pool" parameter as well would be beneficial.

[JonathanTron]

Thanks for reporting it, if it creates confusion and issue on your side it's definitely a bug. I'll wait for the CI run to finish and publish a 0.9.1 release.