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 1gXD8e-0001HJ-Op for pgsql-general@arkaria.postgresql.org; Wed, 12 Dec 2018 22:37:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gXD8d-0008Gt-Eq for pgsql-general@arkaria.postgresql.org; Wed, 12 Dec 2018 22:37:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gXD8b-0008Fs-Mm for pgsql-general@lists.postgresql.org; Wed, 12 Dec 2018 22:37:55 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gXD8X-0003pY-Ob for pgsql-general@lists.postgresql.org; Wed, 12 Dec 2018 22:37:53 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id C242F22028 for ; Wed, 12 Dec 2018 17:37:47 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute2.internal (MEProxy); Wed, 12 Dec 2018 17:37:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:references:date:subject:in-reply-to; s=fm1; bh=+B4 fi1rOijElE9awo7eZGKMa6otCdmRHLj0Ckf1cOl0=; b=QoRYgQt64QpndrFHvhO ZRkFZijmEpI3U8y8Ey8apefWkwf3wLI5ZoCj2B3tChEZd/RwXHTDKHK7In6zlDvw zTIkerD5PYz0/x9W7jZr085HONZKBzTIgj/P8XyCCUJNg+hpqsLfG51t+ypGh7aA ZoFlOM28Y2cg6cXbO9H93cAD5LdUrX++80YqA+AVczi6QpcJRdzsVmNYbpZCF/if XssK//xzqlFG9dDZJevdSI/V/GGsb2i/uu/C47UAsf2PMzASI9+IT2Opc/8d86rx wVFWfruIU+6KaqKETEoAFpN79C1z6dAAc/XG8YgZIW1/cuKmKz/yGizi9qiO6Qsk H5Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=+B4fi1rOijElE9awo7eZGKMa6otCdmRHLj0Ckf1cO l0=; b=U7iNGkj17K1vlOlDzeSCUXjlQQusT6DS3Bvj9w8lpISfIOpCKX8zwKAmb BZp/fTsL8DIPHzOefZvwo+W4qKVk8RTaTFyq0UzxOFKHc/13w4+4HpvsxBv/sJuE vrJFD3ZO1nFQwaEB+xr6DjVZdpuvmlfe+ZCg9We/TXD73qQ88pbTjhMPXWHV+4P0 MhF9/USWMqQKOGkalCN/HBSLgqsvrUGEp7OeZAqLjMW1cmrn97Jp/9VZIDDLFUyA RYmTciapd4NkLP7ONzopEplSbLe+OCFkS8xLWN0UW6OkeN5ONSLyj+POwgK5a3IR +fdD0x+9p+fFDIMWsChmSkoRh2Bqw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudehtddgjedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecunecujfgurhepkffhvfgggfgtofhffffujgesrgejreerredtjeenucfhrhhomh eptfgrvhhiucfmrhhishhhnhgruceoshhrkhhrihhshhhnrgesfhgrshhtmhgrihhlrdgt ohhmqeenucfrrghrrghmpehmrghilhhfrhhomhepshhrkhhrihhshhhnrgesfhgrshhtmh grihhlrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 4335641AC; Wed, 12 Dec 2018 17:37:47 -0500 (EST) Message-Id: <1544654267.3583234.1607577016.1555678D@webmail.messagingengine.com> From: Ravi Krishna To: pgsql-general@lists.postgresql.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_154465426735832342" X-Mailer: MessagingEngine.com Webmail Interface - ajax-2f590f9a References: Date: Wed, 12 Dec 2018 17:37:47 -0500 Subject: explain analyze cost In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --_----------=_154465426735832342 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" I am running explain analyze cost on a SQL which reads from two large tables (122mil and 37 mil). The query is an UPDATE SQL where we use derives table in the from clause and then join it back to the table being updated. The explain analyze cost itself is taking forever to run. It is running for the last 1 hr. Does that actually run the SQL to find out the impact of I/O (as indicated in COSTS). If not, what can cause it to run this slow.__ --_----------=_154465426735832342 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8"
I am running explain analyze cost on a SQL which reads from two large tables (122mil and 37 mil).  The query is an UPDATE SQL where we use derives table in the from clause and then join it back to the table being updated.

The explain analyze cost itself is taking forever to run. It is running for the last 1 hr. Does that actually run the SQL to find out the impact of I/O (as indicated in COSTS). If not, what can cause it to run this slow.

--_----------=_154465426735832342--