[web-devel] [Yesod] [persistent] [postgres] PoolExhaustedException in Persistent

Max Cantor mxcantor at gmail.com
Fri Nov 4 17:42:06 CET 2011


how would I tell?

max

On Nov 5, 2011, at 12:38 AM, Michael Snoyman wrote:

> This is being caused by runSqlPool, which uses runPool' from the pool
> package. Switching to runPoolAllocate would mean an extra connection
> would be created when the pool is exhausted.
> 
> Getting a PoolExhaustedException is probably an indication that you
> need to bump the size of your connection pool. What is it set at
> currently?
> 
> On Fri, Nov 4, 2011 at 8:20 AM, Max Cantor <mxcantor at gmail.com> wrote:
>> Hi,
>> 
>> I'm getting PoolExhaustedException's on persistent-postgres.  I'm on persistent 6 and yesod 9.  any ideas where to start looking for a source?
>> 
>> my runDB is straight out of the foundation:
>> 
>> runDB f = liftIOHandler $ fmap connPool getYesod >>= Settings.runConnectionPool f
>> 
>> thanks,
>> max
>> 
>> 




More information about the web-devel mailing list