Coerce max_connections to an integer
Coerce max_connections to an integer

max_connections must be a non-zero integer. It so happens that calling
to_i on things that aren't integers returns 0, which should fail
validation correctly.

Otherwise, if you specify the max_connections attribute as an integer,
the existing (convoluted) check fails because you can't to_i a Fixnum.

NREL-cookbooks/postgresql,inetsys/postgresql,chiemi627/postgresql,NREL-cookbooks/postgresql,pronix/postgresql,eheydrick/postgresql,sous-chefs/postgresql,Unholster/postgresql,hw-cookbooks/postgresql,dwashko/chef-postgresql,h4ck3rm1k3/postgresql,h4ck3rm1k3/postgresql,dwashko/chef-postgresql,ozzyogkush/postgresql,GitBytes/postgresql,GitBytes/postgresql,wearefuturegov/postgresql,ozzyogkush/postgresql,gsaslis/postgresql,patcon/postgresql,patcon/postgresql,wearefuturegov/postgresql,gsaslis/postgresql,Unholster/postgresql,rastasheep/postgresql,hw-cookbooks/postgresql,rastasheep/postgresql,livepy/postgresql,eheydrick/postgresql,yakara-ltd/postgresql,livepy/postgresql,inetsys/postgresql,chiemi627/postgresql,sous-chefs/postgresql,pronix/postgresql,yakara-ltd/postgresql