Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yl0c4-0006pA-6Q for pgsql-performance@arkaria.postgresql.org; Wed, 22 Apr 2015 19:47:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yl0c3-0002Uh-FP for pgsql-performance@arkaria.postgresql.org; Wed, 22 Apr 2015 19:47:11 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yl0c1-0002TD-VX for pgsql-performance@postgresql.org; Wed, 22 Apr 2015 19:47:10 +0000 Received: from nm16-vm6.bullet.mail.ne1.yahoo.com ([98.138.91.109]) by makus.postgresql.org with esmtps (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Yl0by-0000mY-OF for pgsql-performance@postgresql.org; Wed, 22 Apr 2015 19:47:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s2048; t=1429732023; bh=dLxA9zb0C6ukh3PnTgpZfaVyO6ZhCUco3HYjdS+LEpk=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=ZlTevnOt6uCR+IVH9DoFOVJFjMMfJaVCidrqz4UhbBOrtluekXROCmzVwVwSF3QwtZlCgUrzrPLZ50U6fKSrwyZKnhp8Dh1vJlm5SBYLgZsskCGriMl6Q/qJjUO6BA9dYLmmcq+p5UfCjDUkac7ymazcwIIRDI6SJYU6vjxm7MXZIfxyefi8XhItDagz+RUpnqHU8Q2MJytW2OqFVJzIN38ERy33et+goFXyPpBGx+Tt81boXVs0Tf9FGPPULx8DhgvNP+ax3ROgR4DPJifsCtXWMgDHhCJtZRdecERoVhCsio2PnPVvQPSzPNysrjEPCPOljcWmypmU7jeCFnpucw== Received: from [98.138.101.131] by nm16.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2015 19:47:03 -0000 Received: from [98.138.87.12] by tm19.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2015 19:47:03 -0000 Received: from [127.0.0.1] by omp1012.mail.ne1.yahoo.com with NNFMP; 22 Apr 2015 19:47:03 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 876943.10226.bm@omp1012.mail.ne1.yahoo.com X-YMail-OSG: WzU8g7UVM1n369IsMUguNyueXh2RVmVmdKl7OqtwgMN5OLytfmkdBVnOq.dZ6.f 0vU_mwN1nxc15XwbeatrL3Snpnd3dX2MDbZD0zbqWRRIqt8zHIQk4Vzozhvw9Qc0wjKen__i9iNc 3NKWwFbWJNFsBYjtCtZHI0JaZ1wV1vqi2n.B5dEEPvSMbIvrXS1SN5PEWFDirsfF9olcTifhigKU KsTjBidj5wk5U0R3mwb6Q.g99s0iQkSNKLjA5cVqxzLCKPoe7CMBhmoiFG5CRsiP6g94ghGfNAtB NbcIg3sIxmL8U_hS6SUQsoJ7M8AuViNOBCDEe53kI2rzMSVL3qSg0F8gD5XkTFmj0LW9WEH39Cag 94DHJ_2bR2dyuu75WV2XjdNLP_dV7gEKWbIhEXrmSuJKtX_MrH0ueHOln9ZGVyAyXCfhvOmZ4INL 0_YHilHP6yrThmLYf8c_DH9jy9UX58VlYPKRDY9qakmvE8gOSaMz23hb9CeKoHfzBrUs1TXJOJPo e0ToFDtRzOPyuP0_4A4h.lw-- Received: by 98.138.105.205; Wed, 22 Apr 2015 19:47:03 +0000 Date: Wed, 22 Apr 2015 19:47:03 +0000 (UTC) From: Kevin Grittner Reply-To: Kevin Grittner To: Andomar , "pgsql-performance@postgresql.org" Message-ID: <223706913.2307849.1429732023067.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <5537DC6D.2010300@aule.net> References: <5537DC6D.2010300@aule.net> Subject: Re: Query plan with missing timespans MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Length: 435 X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Andomar wrote: > In the output of "explain analyze" below, what was the query > doing between actual time 1.426 and 17.077? Looping through 384 index scans of tbl, each taking 0.040 ms. That's 15.36 ms. That leaves 0.291 ms unaccounted for, which means that's about how much time the top level nested loop took to do its work. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance