Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bfDZX-0000LE-UW for pgsql-performance@arkaria.postgresql.org; Wed, 31 Aug 2016 22:01:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bfDZX-0002Mo-86 for pgsql-performance@arkaria.postgresql.org; Wed, 31 Aug 2016 22:01:27 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bfDZV-0002Hp-KL for pgsql-performance@postgresql.org; Wed, 31 Aug 2016 22:01:25 +0000 Received: from mail-qk0-x230.google.com ([2607:f8b0:400d:c09::230]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bfDZT-0007TE-5J for pgsql-performance@postgresql.org; Wed, 31 Aug 2016 22:01:25 +0000 Received: by mail-qk0-x230.google.com with SMTP id t7so66569833qkh.1 for ; Wed, 31 Aug 2016 15:01:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=Gd+nekv8LBC/uZHGnzl7YOj4ZFyDCWk/xO6sn3amucw=; b=c/oL8B+pwy7kNywoXLHAZdSB0FMk5AMbyJ8lOTdMR/VLCyxu8xOkPo8To1cgpP8yYU 7ppdZ6VOQRtbKU1/X3QdYYSXuKkS1zY4n2I/3jbUlT9BJcSH8YPDM/rmAKHSNaYv8rqe E8siKkzJYPni6dZOmvhBHRYyBkJLLtVOZ47lrLSJ792MUw6LExPJ/6DWkpol2HBivwk6 NmuzkKzh7yfQ5Jq4F5QdyyhIbwk3iy2wgGsBO/hoXTHR+uqLFzj2ID2daxZJTQdn5V1u bqYM3WXIw/B23avG4faT34Rw7dlNNBUKUjagVu9X8A9TL4dGPhZNNKbPXlN4rNVcjIrh hE2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=Gd+nekv8LBC/uZHGnzl7YOj4ZFyDCWk/xO6sn3amucw=; b=VGj0WZFHMx4CsJrXunzL8bUFqePPNukHuqiy/Y/lUtAbMJ8BAoAbrg75LzSadqVcKR 3lrlD8ClisXisu34efEhZu3/MSDJPzEwwsm4ZQspyQMx257/z/uxiY5HtoRCEq0ATCjM sW9A+/bDcmVe53TkCshZ+3WDiLBj1DCJxv1i0obvyhyShLPDgTCGj38sUxYWhFGdbBAx 1VGvomZaS0ragthra1Xa5LPlmLSip6IZRn8H8Ax6ZEF7bRAprHaFsxDjXRBqMMMQWtqk 97XtuDp6uy1cmx5DKk/YID5KQfSbSUAU002sRUigC2ZdJdXNEmBv25FRl1cUM8tbanG2 TbSA== X-Gm-Message-State: AE9vXwPTCen9t6TcfmzhFkf4s8dhbINterSG/YcLs/BV/5XFgmHUDbODa/uNtlVa9ctoqw== X-Received: by 10.55.191.2 with SMTP id p2mr13435248qkf.77.1472680881314; Wed, 31 Aug 2016 15:01:21 -0700 (PDT) Received: from [10.0.1.5] (static-71-126-153-54.washdc.fios.verizon.net. [71.126.153.54]) by smtp.gmail.com with ESMTPSA id v126sm1097249qkh.30.2016.08.31.15.01.20 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 31 Aug 2016 15:01:20 -0700 (PDT) From: Bobby Mozumder Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Possible to find disk IOs for a Query? Message-Id: Date: Wed, 31 Aug 2016 18:01:19 -0400 To: "pgsql-performance@postgresql.org" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-Pg-Spam-Score: -2.7 (--) 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 Is it possible to find the number of disk IOs performed for a query? EXPLA= IN ANALYZE looks like it shows number of sequential rows scanned, but not n= umber of IOs.=20=20 My database is on an NVMe SSD, and am trying to cut microseconds of disk IO= per query by possibly denormalizing. Thank you, -bobby --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance