| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | "Bhupathi, Kaushik (CORP)" <Kaushik(dot)Bhupathi(at)ADP(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Q on SQL Performance tuning |
| Date: | 2019-01-27 14:31:08 |
| Message-ID: | 20190127143108.GK13248@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2019-01-27 16:04:06 | Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? |
| Previous Message | legrand legrand | 2019-01-27 11:28:59 | Re: Q on SQL Performance tuning |