pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Fuhr <mike@fuhr.org>
To: Lane Van Ingen <lvaningen@esncc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pgStatTuple
Date: Fri, 24 Feb 2006 16:13:10 -0700
Message-ID: <20060224231310.GA31534@winnie.fuhr.org> (raw)
In-Reply-To: <EKEMKEFLOMKDDLIALABIIEFECIAA.lvaningen@esncc.com>
References: <EKEMKEFLOMKDDLIALABIIEFECIAA.lvaningen@esncc.com>

On Fri, Feb 24, 2006 at 05:03:58PM -0500, Lane Van Ingen wrote:
> I want to use pgStatTuple to analyze performance problems when visiting user
> sites; it is a good tool. I know how to set it up; but I couldn't find an
> interpretation of what it generates as a result, so I can be sure of
> interpreting its output correctly and fully.

Have you seen README.pgstattuple?  Here's an excerpt:

table_len               -- physical table length in bytes
tuple_count             -- number of live tuples
tuple_len               -- total tuples length in bytes
tuple_percent           -- live tuples in %
dead_tuple_len          -- total dead tuples length in bytes
dead_tuple_percent      -- dead tuples in %
free_space              -- free space in bytes
free_percent            -- free space in %

It can be educational to create a table to play with and watch
pgstattuple's output change depending on what you do (insert, update,
delete, vacuum, etc.).

> Can anyone help? May also require definition of 'tuple' when used in a
> PostgreSQL sense, also.

Tuple, row, and record are generally used synonymously; tuple seems
to be the more common term in discussions of theory.  If that's too
broad a generalization then maybe somebody will provide a more
precise explanation.

-- 
Michael Fuhr



view thread (3+ messages)  latest in thread

Message-ID: <20060224231310.GA31534@winnie.fuhr.org>
Permalink:  ../20060224231310.GA31534@winnie.fuhr.org/
Also on:    postgresql.org/message-id/20060224231310.GA31534@winnie.fuhr.org

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mike@fuhr.org, lvaningen@esncc.com
  Subject: Re: pgStatTuple
  In-Reply-To: <20060224231310.GA31534@winnie.fuhr.org>
  References: <EKEMKEFLOMKDDLIALABIIEFECIAA.lvaningen@esncc.com> <20060224231310.GA31534@winnie.fuhr.org>

* 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