Re: Increasing maximum connection for postgresql 9.2

From: Amardeep Kaur <amardeepkaur88(at)gmail(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Increasing maximum connection for postgresql 9.2
Date: 2014-02-21 13:37:23
Message-ID: CAJ1JmhVxTUGmfd2pTkOLd24F8i0iRgcp8oHY0pFGnjh3n82PNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

The error is
*could not receive data from client: Connection reset by peer*
followed by
*incomplete startup packet*

-Amardeep

On Fri, Feb 21, 2014 at 10:20 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>wrote:

> Amardeep Kaur wrote:
> > I am trying to increase the max_connection from 100 to 5000. I modified
> shared_buffer and changed
> > kernel parameters according to
> > http://www.postgresql.org/docs/9.2/static/kernel-resources.html#SYSVIPC.
>
> As has been mentioned, that is too much.
> There is also an interesting article on the Wiki:
> http://wiki.postgresql.org/wiki/Number_Of_Database_Connections
>
> > When i stress test it with 500 concurrent request, then after 150 - 160
> concurrent connections my
> > database enters into recovery mode and it fails the request. For my
> stress test i am trying to get
> > data from one table.
> >
> > Do you guys have any idea what is causing the problem or if i am missing
> some other configuration?
>
> The database does not go into recovery mode just like that.
> Look into the database log and see if you can find the appropriate
> messages, then
> we can figure out what caused the problem.
>
> Yours,
> Laurenz Albe
>

--
Amardeep Kaur
8130553685

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2014-02-21 14:05:50 Re: Increasing maximum connection for postgresql 9.2
Previous Message Albe Laurenz 2014-02-21 13:20:59 Re: Increasing maximum connection for postgresql 9.2