Re: dsa_allocate() faliure

>>dsa_allocate could not find 7 free pages I just this error message again on all of my worker nodes (I am using Citus 7.4 rel). The PG core is my own build of release_10_stable (10.4) out of GitHub on Ubuntu. What's the best way to debug this? I am running pre-production tests for the next few

Re: Help me in reducing the CPU cost for the high cost query below, as it is hitting production seriously!!

Thanks a lot! I will have a look On Tue, May 22, 2018, 11:53 PM Justin Pryzby wrote: > On Tue, May 22, 2018 at 03:51:44AM -0700, pavan95 wrote: > > Please find the output of explain(analyze,buffers) for the whole query in > > the below link. > > > Seq Scan on res_users

Re: Help me in reducing the CPU cost for the high cost query below, as it is hitting production seriously!!

On Tue, May 22, 2018 at 03:51:44AM -0700, pavan95 wrote: > Please find the output of explain(analyze,buffers) for the whole query in > the below link. > Seq Scan on res_users users (cost=750.92..1,836.69 rows=249 width=15) (actual > time=3.962..17.544 rows=67 loops=1) Not sure but would you

Re: Help me in reducing the CPU cost for the high cost query below, as it is hitting production seriously!!

Hi Justin, Please find the output of explain(analyze,buffers) for the whole query in the below link. Link: https://explain.depesz.com/s/dNkb Thanks in Advance! Regards, Pavan -- Sent from:

Re: Help me in reducing the CPU cost for the high cost query below, as it is hitting production seriously!!

Hi all, Thank you so much for your valuable responses.Tried every aspect which you have said for my sub-query. I hoped a better decrease in cost for my main query. But yes it decreased but not to a great extent. What I felt is to provide the main query and the associated table definitions in

Re: Help me in reducing the CPU cost for the high cost query below, as it is hitting production seriously!!

Hi all, Thank you so much for your valuable responses.Tried every aspect which you have said for my sub-query. I hoped a better decrease in cost for my main query. But yes it decreased but not to a great extent. What I felt is to provide the main query and the associated table definitions in