From: Justin Pryzby <pryzby@telsasoft.com>
To: Bhupathi, Kaushik (CORP) <Kaushik.Bhupathi@ADP.com>
Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: Q on SQL Performance tuning
Date: Sun, 27 Jan 2019 08:31:08 -0600
Message-ID: <20190127143108.GK13248@telsasoft.com> (raw)
In-Reply-To: <A55AA5B30958C74083D731937B524ED685A61BFC@DC2PRMBX06A.ES.AD.ADP.com>
References: <A55AA5B30958C74083D731937B524ED685A61BFC@DC2PRMBX06A.ES.AD.ADP.com>
On Sun, Jan 27, 2019 at 08:43:15AM +0000, Bhupathi, Kaushik (CORP) wrote:
> 2) Is there anyway to know the historical execution plan details of a particular SQL ? Per my understanding so far since there is no concept of shared pool unlike Oracle every execution demands a new hard parse. However wanted to check with experts to know if any extension available on this?
There's also autoexplain, althought I think that's typically configured to only
output plans for queries which longer than a minimum duration.
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, Kaushik.Bhupathi@ADP.com, pgsql-performance@lists.postgresql.org
Subject: Re: Q on SQL Performance tuning
In-Reply-To: <20190127143108.GK13248@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