Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mOkXd-0005LL-Rl for pgsql-performance@arkaria.postgresql.org; Fri, 10 Sep 2021 17:42:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mOkXc-0000dh-Gv for pgsql-performance@arkaria.postgresql.org; Fri, 10 Sep 2021 17:42:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mOkXc-0000dY-8W for pgsql-performance@lists.postgresql.org; Fri, 10 Sep 2021 17:42:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mOkXV-0006uG-46 for pgsql-performance@postgresql.org; Fri, 10 Sep 2021 17:42:19 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 18AHg8TI4078765; Fri, 10 Sep 2021 13:42:08 -0400 From: Tom Lane To: "Michel SALAIS" cc: "'Julien Rouhaud'" , "'postgres performance list'" Subject: Re: sql execution time in pg_stat_statements In-reply-to: <007201d7a667$1516d860$3f448920$@msym.fr> References: <005f01d7a5a6$67784b50$3668e1f0$@msym.fr> <006601d7a5ab$6e01c780$4a055680$@msym.fr> <007201d7a667$1516d860$3f448920$@msym.fr> Comments: In-reply-to "Michel SALAIS" message dated "Fri, 10 Sep 2021 19:12:48 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4078763.1631295728.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 10 Sep 2021 13:42:08 -0400 Message-ID: <4078764.1631295728@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Michel SALAIS" writes: > I thaught that total_time (total_exec_time + total_plan_time) included I= /O but when we have blk_read_time + blk_write_time equals several times t= otal_time it is difficult to continue to think that... That's an interesting report, but on the whole I'd be more inclined to disbelieve the I/O timings than the overall time. Can you create a reproducible test case where this happens? Also, exactly what PG version and pg_stat_statements version are you using? regards, tom lane