RE: Slow Running Queries in Azure PostgreSQL - Mailing list pgsql-performance

From Kumar, Mukesh
Subject RE: Slow Running Queries in Azure PostgreSQL
Date
Msg-id CH0P221MB0474F813698042E79E630621DE3E9@CH0P221MB0474.NAMP221.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Slow Running Queries in Azure PostgreSQL  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-performance
Hi Justin ,

Thanks for your help , After committing 1 parameter , the whole query executed in less than 1 min.



Thanks and Regards,
Mukesh Kumar

-----Original Message-----
From: Justin Pryzby <pryzby@telsasoft.com>
Sent: Wednesday, February 23, 2022 2:57 AM
To: Kumar, Mukesh <MKumar@peabodyenergy.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow Running Queries in Azure PostgreSQL

On Tue, Feb 22, 2022 at 02:11:58PM +0000, Kumar, Mukesh wrote:

>  ->  Hash Join  (cost=6484.69..43117.63 rows=1 width=198) (actual time=155.508..820.705 rows=52841 loops=1)"
>        Hash Cond: (((lms_doc_property_rights_assoc.doc_sid_c)::text =
(lms_doc_propright_status_assoc.doc_sid_c)::text)AND ((lms_property_rights_base.property_sid_k)::text =
(lms_doc_propright_status_assoc.property_sid_c)::text))"

Your problem seems to start here.  It thinks it'll get one row but actually gets 53k.  You can join those two tables on
theirown to understand the problem better.  Is either or both halves of the AND estimated well ? 

If both halves are individually estimated well, but estimated poorly together with AND, then you have correlation.

Are either of those conditions redundant with the other ?  Half of the AND might be unnecessary and could be removed.

--
Justin



pgsql-performance by date:

Previous
From: MichaelDBA
Date:
Subject: Re: Slow plan choice with prepared query
Next
From: Justin Pryzby
Date:
Subject: Re: An I/O error occurred while sending to the backend (PG 13.4)