Message-ID: <2988e92ed6eb90d60014d2f879c73bc9ceaf5d1f.camel@cybertec.at>
Subject: Re: View taking time to show records
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: "Kumar, Mukesh" <MKumar@peabodyenergy.com>,
	"pgsql-performance@postgresql.org"
	 <pgsql-performance@postgresql.org>
Date: Sat, 26 Mar 2022 05:37:38 +0100
In-Reply-To: 
 <CH0P221MB0474CF7EA6C4767FD11B707EDE1A9@CH0P221MB0474.NAMP221.PROD.OUTLOOK.COM>
References: 
	<CH0P221MB04748BF130CDFF2625EDB396DE199@CH0P221MB0474.NAMP221.PROD.OUTLOOK.COM>
	 <3de146f0ea4ae3bab84be8e1c888d64d11ca6606.camel@cybertec.at>
	 <CH0P221MB0474CF7EA6C4767FD11B707EDE1A9@CH0P221MB0474.NAMP221.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.40.4 (3.40.4-3.fc34) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/2988e92ed6eb90d60014d2f879c73bc9ceaf5d1f.camel%40cybertec.at>
Precedence: bulk

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