Skip site navigation (1) Skip section navigation (2)

Re: Postgres Server collapse

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Sistemasvi <sistemasvi(at)aerogal(dot)com(dot)ec>
Cc: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Postgres Server collapse
Date: 2006-11-27 15:33:06
Message-ID: 3085BCC6-4EA6-4A7D-BCC8-4106735F5029@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Carlos,

You should be using a connection pool, if you don't have the memory  
to support 800 connections then it just isn't going to work.

Dave
On 27-Nov-06, at 10:19 AM, Sistemasvi wrote:

> Hello.
>
> I have a postsgresql database with max 500 connections. All  
> development is in Java (View, Model, controller model). The problem  
> is when I have high traffic (about 10 AM) when the database server  
> collapse. The server turn too slow as It havenĀ“t memory and the  
> swap memory increase too much. I must kill all postgres connections  
> and restart postmaster service.
>
> I have only one connection by web session. It is good or bad?
> I have already increased the number of connections to 800 in the  
> postgres and sysctl configuration file.
>
> My server is linux Red Hat and Postgres database V8
>
> Which can be the problem?.
>
>
> Carlos
>
>
>

In response to

pgsql-jdbc by date

Next:From: Mark LewisDate: 2006-11-27 15:34:37
Subject: Re: Postgres Server collapse
Previous:From: John S.AbrahamDate: 2006-11-27 15:22:02
Subject: Re: Backup with Java

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group