From: Giuseppe Broccolo <giuseppe.broccolo@2ndquadrant.it>
To: Xenofon Papadopoulos <xpapad@gmail.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: pg_statio_all_tables columns
Date: Mon, 30 Sep 2013 18:30:43 +0200
Message-ID: <5249A733.5070904@2ndquadrant.it> (raw)
In-Reply-To: <CANL7jAQ3d_m8PnxFOkn2uVaS-R3sWTiRNL4ZrjgnpEvROEpfrw@mail.gmail.com>
References: <CANL7jAQr_rrkz2u+OS=mwvh1Aj5S5uTYSviu+vDPa-cc4DxiZQ@mail.gmail.com>
<52498D71.8010002@2ndquadrant.it>
<CANL7jAQ3d_m8PnxFOkn2uVaS-R3sWTiRNL4ZrjgnpEvROEpfrw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Il 30/09/2013 16:41, Xenofon Papadopoulos ha scritto:
> Should this ratio stay low even in the case of a write-heavy table?
Yes, in my opinion. Before data manipolation, database pages are moved
on the shared buffer. heap_blks_read and heap_blks_hit are involved in
those operations, not directly in data persistance on hard driver.
Giuseppe.
--
Giuseppe Broccolo - 2ndQuadrant Italy
PostgreSQL Training, Services and Support
giuseppe.broccolo@2ndQuadrant.it | www.2ndQuadrant.it
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: giuseppe.broccolo@2ndquadrant.it, xpapad@gmail.com
Subject: Re: pg_statio_all_tables columns
In-Reply-To: <5249A733.5070904@2ndquadrant.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox