From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: vacuumdb not letting me connect to db |
Date: | 2021-02-05 16:11:18 |
Message-ID: | a988e21a-7f1c-8480-235a-1c5cf7ba6b3c@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Obviously... don't use 300 threads.
On 2/5/21 2:15 AM, Atul Kumar wrote:
> ok, How do I resolve it ?
>
> Any suggestions ?
>
> On 2/5/21, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>> Your problem screams "IO saturation".
>>
>> On 2/4/21 12:07 PM, Atul Kumar wrote:
>>> There is no error message, when I try to connect the database while
>>> running vacuumdb with 300 jobs, it gets stuck.
>>>
>>> On Thursday, February 4, 2021, Ravi Krishna <rkrishna_pg(at)aol(dot)com
>>> <mailto:rkrishna_pg(at)aol(dot)com>> wrote:
>>>
>>> >The CPU and RAM are normal even on 300 jobs ( only 1-4% of
>>> consumption)
>>> >but I don’t understand one thing here that if max_connections is set
>>> to 700 then
>>> >why I am not able to connect the db. As the running jobs (300) are
>>> lesser than
>>> >half of max_connections.
>>>
>>> Please paste the error message
>>>
>> --
>> Angular momentum makes the world go 'round.
>>
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2021-02-05 16:22:41 | Re: vacuumdb not letting me connect to db |
Previous Message | Thorsten Schöning | 2021-02-05 16:02:23 | Less efficient query plan after merging tables |