whatever you choose it always starts with one and grows with the number of concurrent requests up to the value of pools (the max number of concurrent pools). So pools should be the max number of concurrent requests you expect. That is the max value of
<number of requests/second> / <average time per request in seconcds> On Feb 15, 6:22 pm, Baron <[email protected]> wrote: > hi ionel, > I was the one who switched from mysql to postgres to avoid that error > and haven't had any problems since. > Maybe you could try switching from postgres to mysql! > > Massimo I'm not using pools at the moment but it sounds like a good > idea. How would I determine a reasonable number of pools to use? > > Baron > > On Feb 16, 7:28 am, mdipierro <[email protected]> wrote: > > > I suggest you use connection pools. It is designed to reuse connection > > and will make your application much faster. > > > Just add SQLDB(....,pools=20) > > > Massimo > > > On Feb 15, 10:05 am, ionel <[email protected]> wrote: > > > > Hello Massimo, > > > > I don't use connection pools. > > > I use web2py 1.55.2 with Postgresql 8.3. The max_connections parameter > > > was set at 100 in postgresql.conf. I changed the value to 200. I hope > > > this will fix the problem. > > > > My application is not in production. I get this error when I develop > > > and try the results. > > > > Thanks for help > > > > On Feb 15, 8:50 am, mdipierro <[email protected]> wrote: > > > > > Are you using connections pools? > > > > > db=SQLDB(...,pools=<n>) > > > > > try increase the max number of connections: > > > > >http://www.postgresqlforums.com/forums/viewtopic.php?f=15&t=531 > > > > > web2py closes connections automatically when a thread ends unless you > > > > have pools. > > > > > Massimo > > > > > On Feb 15, 2:19 am, Fran <[email protected]> wrote: > > > > > > On Feb 15, 5:22 am, ionel <[email protected]> wrote: > > > > > > > OperationalError: FATAL: connection limit exceeded for > > > > > > non-superusers > > > > > > Do I need to close the connection explicitly somewhere? > > > > > > Interesting, someone previously had the same kind of problem with > > > > > MySQL which they fixed by moving to > > > > > PostgreSQL:http://groups.google.com/group/web2py/browse_thread/thread/7019f65977... > > > > > > For the issue to get fixed, I imagine that people would need to know: > > > > > (1) The exact versions of Web2Py/PostgreSQL/Python > > > > > (2) Your code > > > > > > F --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
