From: Justin Pryzby <pryzby@telsasoft.com>
To: Kumar, Mukesh <MKumar@peabodyenergy.com>
Cc: pgsql-performance@postgresql.org, MUKESH KUMAR <mukesh.kumar14@tcs.com>
Subject: Re: Query Tunning related to function
Date: Sat, 16 Apr 2022 22:13:15 -0500
Message-ID: <20220417031315.GY26620@telsasoft.com> (raw)
In-Reply-To: <CH0P221MB04744DB33957A93BB2F7782EDEEF9@CH0P221MB0474.NAMP221.PROD.OUTLOOK.COM>
References: <CH0P221MB04744DB33957A93BB2F7782EDEEF9@CH0P221MB0474.NAMP221.PROD.OUTLOOK.COM>
On Thu, Apr 14, 2022 at 06:03:33AM +0000, Kumar, Mukesh wrote:
> We are running the below query in PostgreSQL and its taking approx. 8 to 9 sec to run the query.
>
> Query - 1 ...
>
> The explain plan and other details are placed at below link for more information. We have checked the indexes on column but in the explain plan it is showing as Seq Scan which we have to find out.
>
> https://explain.depesz.com/s/Jsiw#stats
There's a list of information to provide in the postgres wiki, and people here
sent you a link to that wiki page on Feb 27, Mar 1, and Apr 12. Your problem
report is still missing a lot of that information. Asking for it piece by
piece would be tedious.
--
Justin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com, MKumar@peabodyenergy.com, mukesh.kumar14@tcs.com
Subject: Re: Query Tunning related to function
In-Reply-To: <20220417031315.GY26620@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox