Neil Palima

I encountered this issue now. It was working yesterday. What can be the reason? I'm using the latest version inside an AWS EC2 instance.

Did you find a way to set connection pool?

I tried using `max` but it does not seem to affect the number of queries being processed concurrently.

Is there any hack for this to be solve in the mean time?