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 1gXDZh-0002dd-Uh for pgsql-general@arkaria.postgresql.org; Wed, 12 Dec 2018 23:05:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gXDZg-0007JY-7R for pgsql-general@arkaria.postgresql.org; Wed, 12 Dec 2018 23:05:52 +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 1gXDZf-0007JR-VM for pgsql-general@lists.postgresql.org; Wed, 12 Dec 2018 23:05:52 +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 1gXDZd-0004UN-MO for pgsql-general@lists.postgresql.org; Wed, 12 Dec 2018 23:05:51 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 244A12213E; Wed, 12 Dec 2018 18:05:48 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 12 Dec 2018 18:05:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=W/nd+AmF4SeE6TRN0bOGt62RpHv c2IGKFeu4pWSDLls=; b=Sl49wlcr34wHN4onFhMnxYlstvxLktinipZx7fwCJQf O7bLQj02tgv3M2j6g03wr5jP7gMZReunUn9biwSlNxWBOgVgyZICijN3Mq1mEMTF LMt+pzMRPqGGcKf/p8Xqt7jiXZW7V5mBQhX2ftIPa+LpWG9HQguFfAQjXoBqUDn7 wTbQnJ4NUFX13aiPp/HKQ3FVk0XHgxGqSRc2YOL2tdxLzO/CymN1yDkgM46NxhAb UcW5YtpY9CCJWOQW4yvRYyTKqbs9ZNLJic5Db5GRNXXPFfAMFm50fV6kCywR8P6M Gj7s2U7kiMMAzOKeuX4G9JCZKlmOZAHRxjnzNl3gP8A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=W/nd+A mF4SeE6TRN0bOGt62RpHvc2IGKFeu4pWSDLls=; b=NyRr4Fb2BEOGHDQ/buUCXd 4g5WZnJvaJCp0MyA9C/l2q/y/wjP+Pd7atX22iKURwfOyTFmbDG49+SB5DMya5d8 LjZ8WzW2N2fx94FpKc2UTLp6xjsHf0omYFgjR/XD41SKvUvGoMo+QmL/XChNiXYA +zV6AiL5OLBVEpDMS9uMc9W26jV2+bx2/9MvYslJkYpNkHihaMhLCd2HcHG0DJF0 EEOeQNydWlZnmYY2ecuyvvn9CsLSk1JCJWasoSddgBf9T6ZEAzdzySluMyrFajZA 9XTuoRrPE+6byqsTMxm1Vxgc2avr1B3w2mXsxBOgpXHEB/2GnFHGZM4yFyLfNH3g == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudehuddgtdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfh ggtggujgesthdtredttddtvdenucfhrhhomheptehnughrvghsucfhrhgvuhhnugcuoegr nhgurhgvshesrghnrghrrgiivghlrdguvgeqnecukfhppeelkedrvddutddrudegtddrud ejudenucfrrghrrghmpehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdr uggvnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from intern.anarazel.de (c-98-210-140-171.hsd1.ca.comcast.net [98.210.140.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 401B8102A0; Wed, 12 Dec 2018 18:05:47 -0500 (EST) Date: Wed, 12 Dec 2018 15:05:45 -0800 From: Andres Freund To: Ravi Krishna Cc: pgsql-general@lists.postgresql.org Subject: Re: explain analyze cost Message-ID: <20181212230545.xg22ufkuqnv4hsbz@alap3.anarazel.de> References: <1544654267.3583234.1607577016.1555678D@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1544654267.3583234.1607577016.1555678D@webmail.messagingengine.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2018-12-12 17:37:47 -0500, Ravi Krishna wrote: > 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.__ Please do not hijack other threads by replying to a message and changing the subject. Just send a new mail to pgsql-general@lists.postgresql.org, or whatever list you want to send an email to. Thanks, Andres