pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Maria L. Wilson <Maria.L.Wilson-1@nasa.gov>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Wilson, Maria Louise (LARC-E301)[SCIENCE SYSTEMS APPLICATIONS] <m.l.wilson@nasa.gov>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: [Fwd: postgres 8.4.1 number of connections]
Date: Mon, 30 Aug 2010 09:53:20 -0400
Message-ID: <4C7BB7D0.3010201@nasa.gov> (raw)
In-Reply-To: <AANLkTikkCJ1embk=i6V06k7sRQqv3WfGGwPLNGTGuMWV@mail.gmail.com>
References: <4C76CEAB.1070308@nasa.gov>
	<AANLkTikkCJ1embk=i6V06k7sRQqv3WfGGwPLNGTGuMWV@mail.gmail.com>

thanks for your response....
we have 3 app servers that attach to this one particular database server.
What kind of load issues did you find on 8.4.1?  I'd be interested in 
anything documented on it - this might make an upgrade a higher priority!

thanks,  Maria

Scott Marlowe wrote:
> On Thu, Aug 26, 2010 at 2:29 PM, Maria L. Wilson
> <Maria.L.Wilson-1@nasa.gov> wrote:
>   
>> we have this application (using jboss/java/hibernate) on linux accessing
>> data on 3 postgres database servers using 8.4.1.
>>
>> One of our many concerns has been the way we handle connections to the
>> database.  java/hibernate handle their own pooling so I understand that
>> using anything else is out of the question.
>>     
>
> It's not impossible to put another connection pooler between hibernate
> and your database server.  May not be useful or better, but it's
> possible.
>
>   
>>  Our jboss configuration
>> currently defaults to 5 connections per database.
>>     
>
> I assume this is for each app server.  How many app servers do you have?
>
>   
>>  On our main database
>> server, we handle 7 of the databases that this application uses.  On
>> this one server, we usually average around 300 - 500 connections to the
>> server.  In our postgres conf file on this particular machine we set the
>> max_connection parameter to 1000.  If we set it to much lower we end up
>> with connection errors.  Any comments or better way to handle this?
>>     
>
> Other than breaking out the databases onto their own server, or trying
> to pool to fewer connections, not really.  OTOH, a db server with
> enough memory can handle having that many connections as long as you
> don't run into any thundering herd issues.
>
> Oh, and you should really update your pgsql to 8.4.4.  8.4.1 had some
> issues with heavy load I ran into last year about this time.  Which is
> why I'm still on 8.3.11
>
> --
> To understand recursion, one must first understand recursion.
>   

view thread (5+ messages)

Message-ID: <4C7BB7D0.3010201@nasa.gov>
Permalink:  ../4C7BB7D0.3010201@nasa.gov/
Also on:    postgresql.org/message-id/4C7BB7D0.3010201@nasa.gov

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: Maria.L.Wilson-1@nasa.gov, scott.marlowe@gmail.com, m.l.wilson@nasa.gov
  Subject: Re: [Fwd: postgres 8.4.1 number of connections]
  In-Reply-To: <4C7BB7D0.3010201@nasa.gov>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox