Re: postgres crashes on insert in 40 different threads - Mailing list pgsql-admin

From Scott Ribe
Subject Re: postgres crashes on insert in 40 different threads
Date
Msg-id 9A8460E0-A087-4002-8153-A7A295C45E4D@elevated-dev.com
Whole thread Raw
In response to Re: postgres crashes on insert in 40 different threads  (Dzmitry <dzmitry.nikitsin@gmail.com>)
List pgsql-admin
On Aug 25, 2013, at 2:04 AM, Dzmitry <dzmitry.nikitsin@gmail.com> wrote:

> Ok,thank you, it's a good point. Need to review & make fixes with what I
> have.

Yes, as suggested I would try just reducing first.

Where connection pooling could help is if your load across all those rails apps is not spread out evenly, but varies
overtime such that there is *no* single small number of workers that is right for all conditions. Because the same
commentsabout no benefit from tons of threads applies to the pg server as well: so 110 connections simultaneously doing
workis not likely to be better than some smaller number... 

--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice






pgsql-admin by date:

Previous
From: Dzmitry
Date:
Subject: Re: postgres crashes on insert in 40 different threads
Next
From: Ed Tarento
Date:
Subject: Root partition full of files in /var/lib/postgresql/9.1/main/pg_xlog