From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | "Kumar, Mukesh" <MKumar(at)peabodyenergy(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: View taking time to show records |
Date: | 2022-03-26 04:37:38 |
Message-ID: | 2988e92ed6eb90d60014d2f879c73bc9ceaf5d1f.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, 2022-03-25 at 14:07 +0000, Kumar, Mukesh wrote:
> > [recommendation to fix the estimate]
> >
> > Perhaps it is also enough to blindly disable nested loop joins for the whole query,
> > rather than doing the right thing and fixing the estimates:
> >
> > BEGIN;
> > SET LOCAL enable_nestloop = off;
> > SELECT ...;
> > COMMIT;
>
> Thanks for the below suggestion , When I ran the query with the parameter , it is taking only 1 sec.
>
> So could you please let me know if I can put this parameter to OFF . at database and it will not
> create any issues to queries running in database.
That will very likely cause problems in your database, because sometimes a nested loop join
is by far the most efficient way to run a query.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Rambabu g | 2022-03-29 18:04:18 | HIGH IO and Less CPU utilization |
Previous Message | Kumar, Mukesh | 2022-03-25 14:07:28 | RE: View taking time to show records |