Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gnlSv-0000S7-SL for pgsql-performance@arkaria.postgresql.org; Sun, 27 Jan 2019 14:31:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gnlSt-0008D4-36 for pgsql-performance@arkaria.postgresql.org; Sun, 27 Jan 2019 14:31:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gnlSs-0008Cu-Kk for pgsql-performance@lists.postgresql.org; Sun, 27 Jan 2019 14:31:14 +0000 Received: from mail-it1-x136.google.com ([2607:f8b0:4864:20::136]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gnlSp-0007GQ-Ii for pgsql-performance@lists.postgresql.org; Sun, 27 Jan 2019 14:31:13 +0000 Received: by mail-it1-x136.google.com with SMTP id m62so17012557ith.5 for ; Sun, 27 Jan 2019 06:31:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=2/KwtK2rQJSLbTYIAnGKHy/hiU4OImDSOdp/qJnGUSI=; b=D9bA9u+kPzGEaTjP2jFHgpNgFWgZy2hG7nWNVBWmABOmHA2EpEsPq845GJPibLAUvo Ujr1/14eHg6p33nm/z2zByCPnWiJ4XDpnkw0E6NRlFa7J6R3HlcFiahhhl7bkymQq7h+ 827hf90ZkbcQrUXOe9eNVubL/xVJqzxvbvGrUvC/CKwuCj+iNM3nCG4XeptHEMimmBaL Ou97EdFJl6IX02X7IznQx4RfdACfzVh/TpgfOu0YMjC9KLY+UdvGBYO3sNwgMl4MLhdC xidzz3E7GOC/SZeBO+TwrLPmlfueAB0aOHF4q1v6gzIn1OT2ehYzQvXniXS+HgZM8/Jr xoFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=2/KwtK2rQJSLbTYIAnGKHy/hiU4OImDSOdp/qJnGUSI=; b=BKZto3F7grIdsVOniqRQBX6ooZjGFDvQP92L+BBhv3pxPuKUWSYxu+zitmlDDz6h7Z M//Oegy6jidoILiLYgmvFn0ZKxYmGysMTtv2J8jRz5IpzV20HpjlWVe+NINOTLNM/U8U hmeU1C9j17lFfMAQq5zKWZT0aeS99LPVBPjlhcU/DQxJOyrml/7N9bCEh3aiP7k4qbb9 oDo09RRA0UpGhsjL12cF2FNV9Uw5KHYcoQGYqxno1dBhV9wqKHkFRl8+9rcHimr7gNKw pKIoFTLOJD08mn3W9SZc/JE9DqdtCXOqvANr6zGlohz8FRZJ5zQhWFJTXmi3cahFmYKr vCnQ== X-Gm-Message-State: AJcUukevH20RSNASvCWIwvs/ayCJ9BivR4oJAtY6hPZk5WUvN9lAerVo KeD2RYqkt+832iMZfQiF3Sdv0A== X-Google-Smtp-Source: ALg8bN5Z1I3HSkLRmXb2EvISokghbxwmDJoEFxpdOEmp+LKIBji0Kyf9O1oxeA4VDoxPLfhVwh/ScA== X-Received: by 2002:a24:5946:: with SMTP id p67mr8699472itb.46.1548599470504; Sun, 27 Jan 2019 06:31:10 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id n143sm15700463itn.42.2019.01.27.06.31.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Jan 2019 06:31:09 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id 822958011F6; Sun, 27 Jan 2019 08:31:08 -0600 (CST) Date: Sun, 27 Jan 2019 08:31:08 -0600 From: Justin Pryzby To: "Bhupathi, Kaushik (CORP)" Cc: "pgsql-performance@lists.postgresql.org" Subject: Re: Q on SQL Performance tuning Message-ID: <20190127143108.GK13248@telsasoft.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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