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 1mRyx4-0004qK-Rf for pgsql-performance@arkaria.postgresql.org; Sun, 19 Sep 2021 15:41:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mRyx3-0003GJ-Pd for pgsql-performance@arkaria.postgresql.org; Sun, 19 Sep 2021 15:41:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mRyx3-0003GA-H1 for pgsql-performance@lists.postgresql.org; Sun, 19 Sep 2021 15:41:57 +0000 Received: from mout.kundenserver.de ([212.227.126.131]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mRywy-0006AN-0G for pgsql-performance@postgresql.org; Sun, 19 Sep 2021 15:41:57 +0000 Received: from ANAT ([78.197.128.121]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.168]) with ESMTPSA (Nemesis) id 1N3Gok-1mrvqh0qXK-010I4V; Sun, 19 Sep 2021 17:41:49 +0200 From: "Michel SALAIS" To: "'Tom Lane'" Cc: "'Julien Rouhaud'" , "'postgres performance list'" References: <005f01d7a5a6$67784b50$3668e1f0$@msym.fr> <006601d7a5ab$6e01c780$4a055680$@msym.fr> <007201d7a667$1516d860$3f448920$@msym.fr> <4078764.1631295728@sss.pgh.pa.us> In-Reply-To: <4078764.1631295728@sss.pgh.pa.us> Subject: RE: sql execution time in pg_stat_statements Date: Sun, 19 Sep 2021 17:41:48 +0200 Message-ID: <000001d7ad6c$dc44d250$94ce76f0$@msym.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJfVqXLzTD3tJt7ImS9sFGS32Fv3QH0n7V9AjP2INACQvqRvgJgvkG4qlXIYTA= Content-Language: fr X-Provags-ID: V03:K1:6lWNVM7dJ4OOYEVJyjWNVVrm1tyXjUufw77HAoihKLrxadwoUyo lLO96Zmq0oJYjIj2WV5LdyMNdhhISA1o2Cevp/40c8KlG1WK8rcsQWFHI1SlR5Os9LTai3e 5FdBGCKIxPPMZnYaHC3Zk5Vhx4qTNtxjGBqzMj7WI2yPk8jmcew5kyhw/Zs4Q6NupByWQ8j imoUdqzk7uS9LciCzImhQ== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:2UwcbQ8XGKU=:0e/IuIVYJDiwmQx9U4QXP6 j0TVJKH0FSfeozSPhHdwSF87TatjbXv0tOMw61fnEtrD79XmnXsws/hnEX4VBxs/df+4Vni2r Bk1O82kB8K1xWNZdk8SQYcvvQ2RKX6naX7zyThSZyqQfLE4k26JfhhQ6f8MkSwdwVAtP0GUmo rS7hiMvxqixxhyNr0FpKCvw+NnmaEWBOuoy0+adG/OKFtiTZIWuEFBOvpGdxlpmy6kMRKRYgD FIaIAhxTW7pGoLYWQt7GAvG0slnr2Q81aowprzw4GJMzhKhhuAc4WJGhbJI3ui2Peu3Zi8TiQ HPxpRS0KMj0yF7avkTGArFQnzDcsCPSB2axjp8+vewA0ct1I07/m49A9q6KRnKQqiThE9dVQX cVnG1umrWq6ILgFvA2mG0CrgaK/zjN3oLURDnMGiG3Sc1jOAVKaZdSvlArdAJQzHbDyvk8RIU vmsbND/L1CGwXHOmoMGCasY3P2e/ZmTK4GN7dBS0Pt19gatdAUnwI9wIXAIpVK5Z37sWodiS2 S/zBv/qumekyIYRTmy/M/bm8MHHcBJin5cAxZzz9OG7V1O7nUNqmHc/HatP6YCIoH+nCZLsUd S4U6QSmfaMX7jLRwDyM94z+84k7zHkcdr0lT90xyzRXhjvnO4hHhYHJQFKtuDDdSeUG0tVAsI uShjjOpE0jHVKybeq8CCkEQOhy+BF/jIsfBVCLVuRSu9DXrIodISvjld/2CxoMMQyMmFGg3LD pbP/LpqebfR7Zr1z2uglGHvWaxLsw+6xDHWyIQ== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Tom, I was out of this list for a while. Unfortunately, I have now no access to the server where I have seen = this. Best regards Michel SALAIS -----Message d'origine----- De=A0: Tom Lane =20 Envoy=E9=A0: vendredi 10 septembre 2021 19:42 =C0=A0: Michel SALAIS Cc=A0: 'Julien Rouhaud' ; 'postgres performance = list' Objet=A0: Re: sql execution time in pg_stat_statements "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 total_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