Re: vacuumdb not letting me connect to db

On 2021-02-06 12:54:11 -0600, Ron wrote: > On 2/6/21 6:06 AM, Atul Kumar wrote: > > Hi Gavan, > > Thanks for providing the details, I need more clarification on this as how > should I analyze that what should be ideal no. of connections should we > set > to avoid IO overhead base

Re: vacuumdb not letting me connect to db

On 2/6/21 6:06 AM, Atul Kumar wrote: Hi Gavan, Thanks for providing the details, I need more clarification on this as how should I analyze that what should be ideal no. of connections should we set to avoid IO overhead based on the available hardware resources. How to do this calculation ?

Re: vacuumdb not letting me connect to db

> On Feb 5, 2021, at 9:37 AM, Ron wrote: > >> On 2/5/21 10:22 AM, Rob Sargent wrote: >> >> >>> On 2/5/21 9:11 AM, Ron wrote: >>> Obviously... don't use 300 threads. >>> >> No, no Ron. Clearly the answer is more CPUs > > I hope you're being sarcastic. > > -- > Angular momentum makes the

Re: vacuumdb not letting me connect to db

On 6 Feb 2021, at 23:06, Atul Kumar wrote: Thanks for providing the details, I need more clarification on this as how should I analyze that what should be ideal no. of connections should we set to avoid IO overhead based on the available hardware resources. How to do this analysis properly is

Re: vacuumdb not letting me connect to db

Hi Gavan, Thanks for providing the details, I need more clarification on this as how should I analyze that what should be ideal no. of connections should we set to avoid IO overhead based on the available hardware resources. How to do this calculation ? Note: even during 300 threads, my RAM util

Re: vacuumdb not letting me connect to db

On 6 Feb 2021, at 3:37, Ron wrote: On 2/5/21 10:22 AM, Rob Sargent wrote: On 2/5/21 9:11 AM, Ron wrote: Obviously... don't use 300 threads. No, no Ron.  Clearly the answer is more CPUs I hope you're being sarcastic. A reasonable conjecture… though there is the consideration that 300 CP

Re: vacuumdb not letting me connect to db

On 2/5/21 10:22 AM, Rob Sargent wrote: On 2/5/21 9:11 AM, Ron wrote: Obviously... don't use 300 threads. No, no Ron.  Clearly the answer is more CPUs I hope you're being sarcastic. -- Angular momentum makes the world go 'round.

Re: vacuumdb not letting me connect to db

On 2/5/21 9:11 AM, Ron wrote: Obviously... don't use 300 threads. No, no Ron. Clearly the answer is more CPUs

Re: vacuumdb not letting me connect to db

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 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

Re: vacuumdb not letting me connect to db

ok, How do I resolve it ? Any suggestions ? On 2/5/21, Ron 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

Re: vacuumdb not letting me connect to db

>There is no error message, when I try to connect the database while >running vacuumdb with 300 jobs, it gets stuck. But you mentioned max connection which now seems to be a red herring. Based on your description, the impression I got is that you are getting "sorry, too many clients already" e

Re: vacuumdb not letting me connect to db

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 > wrote: >The CPU and RAM

Re: vacuumdb not letting me connect to db

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, Ron wrote: > On 2/4/21 5:26 AM, Atul Kumar wrote: > > Hi, > > I have 160 GB of RAM, postgres 9.6 is running on the server. > > after upgrade I ran the

Re: vacuumdb not letting me connect to db

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 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_co

Re: vacuumdb not letting me connect to db

>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

Re: vacuumdb not letting me connect to db

What about disk IO?  That's what really gets saturated when running 300 threads. On 2/4/21 11:00 AM, Atul Kumar wrote: Hi, 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

Re: vacuumdb not letting me connect to db

On 2/4/21 5:26 AM, Atul Kumar wrote: Hi, I have 160 GB of RAM, postgres 9.6 is running on the server. after upgrade I ran the below command: "/usr/edb/as9.6/bin/vacuumdb" -U 'enterprisedb' --verbose --all -j 300 --analyze-only after running that command I was not able to connect the database

Re: vacuumdb not letting me connect to db

Hi, 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. Regards Atul On Thursday, Februa

Re: vacuumdb not letting me connect to db

On Thu, 2021-02-04 at 16:56 +0530, Atul Kumar wrote: > I have 160 GB of RAM, postgres 9.6 is running on the server. > > after upgrade I ran the below command: > > "/usr/edb/as9.6/bin/vacuumdb" -U 'enterprisedb' --verbose --all -j 300 > --analyze-only > > after running that command I was not abl

vacuumdb not letting me connect to db

Hi, I have 160 GB of RAM, postgres 9.6 is running on the server. after upgrade I ran the below command: "/usr/edb/as9.6/bin/vacuumdb" -U 'enterprisedb' --verbose --all -j 300 --analyze-only after running that command I was not able to connect the database using psql for few minutes. After 20-