From: | Jorge Augusto Meira <jmeira(at)c3sl(dot)ufpr(dot)br> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Problems with max_connections parameter |
Date: | 2010-12-06 12:47:53 |
Message-ID: | AANLkTimdAcRvgT2PrtnxkR6jRdOPH5G0Jadkv4am7KzA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi
Thanks for the answers.
Really, I didn't showed you basic informations.
I used the PostgreSQL 8.4. The server configuration was:
Processor: Intel Xeon Processor W3570 Quad Core Processor
Mem: 20GB
Network Interface: Gigabit
HD: 12 x 1 TB (RAID1+0)
OS: Debian GNU/Linux, kernel 2.6.26-2-64
The client machines has similar configuration.
The error message was:
"Erro Conexão: A tentativa de conexão falhou."
or
"Erro Conexão: FATAL: connection limit exceeded for non-superusers"
I used the logs of my java application used to simulate the clients.
Thanks
Jorge
On Fri, Dec 3, 2010 at 12:54 PM, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov
> wrote:
> Euler Taveira de Oliveira <euler(at)timbira(dot)com> wrote:
>
> > Talking about your problem, are you sure you're not reaching
> > max_connections?
>
> It also strikes me that from the minimal information given, it might
> be possible that pid numbers or port numbers are wrapping around
> before the OS is ready to allow re-use. I haven't seen that
> behavior except in machines infected with a worm, but this test
> might be edging into the same territory if it's using a new
> connection for each request. Obviously, nobody who cared about
> performance would use that technique in production, but it rather
> sounds like this test does.
>
> -Kevin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jemshir A.P | 2010-12-06 12:52:04 | BUG #5786: Cannot start pgsql8 application with Previleged account (Admin account) |
Previous Message | Peter Eisentraut | 2010-12-06 12:47:02 | Re: [BUGS] BUG #5662: Incomplete view |