Comment 2 for bug 1572498

I already did, but like i said in the bug description - after restarting postgres, every new execution of "fuel node" command increased the number of connections still being opened so increasing max connections on postgres side only postpones the re-occurrence of this error.
Also - if we know that keystone needs more connections will the max_connections parameter be updated in future releases of fuel?