On Thu, Jul 25, 2013 at 8:39 PM, kris kkvilek...@gmail.com wrote:
On Thursday, July 25, 2013 4:12:50 PM UTC-7, Klauss wrote:
On Thu, Jul 25, 2013 at 7:58 PM, kris kkvil...@gmail.com wrote:
My postgres.conf has a parameter max_connections = 100
That's not only the default, but it's also
On Thu, Jul 25, 2013 at 7:32 PM, kris kkvilek...@gmail.com wrote:
We are running a replicated (multiple machines behind ngnix) Turbogears
2.1.5 App With SA 0.7.8 and postgres 8.4
After a lot of recent usage the system ground to halt and we are receiving
(OperationalError) FATAL: sorry, too
Thanks for the quick reply.
On Thursday, July 25, 2013 3:39:17 PM UTC-7, Klauss wrote:
As the message says, you have too many open connections.
When you have multiple machines, you must either provision your
postgres to be able to handle a full connection pool (max_overflow
preferrably,
On Thu, Jul 25, 2013 at 7:58 PM, kris kkvilek...@gmail.com wrote:
My postgres.conf has a parameter max_connections = 100
That's not only the default, but it's also not really recommended to
push it much higher, so only do so if you really need a big pool on
each machine, and if you're sure
On Thursday, July 25, 2013 4:12:50 PM UTC-7, Klauss wrote:
On Thu, Jul 25, 2013 at 7:58 PM, kris kkvil...@gmail.com javascript:
wrote:
My postgres.conf has a parameter max_connections = 100
That's not only the default, but it's also not really recommended to
push it much higher,
