Re: pgStatTuple

From: "Lane Van Ingen" <lvaningen(at)esncc(dot)com>
To: "Michael Fuhr" <mike(at)fuhr(dot)org>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pgStatTuple
Date: 2006-02-27 13:31:45
Message-ID: EKEMKEFLOMKDDLIALABIEEFMCIAA.lvaningen@esncc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

No, I didn't see the README file. Thanks so much for the info, Michael!

-----Original Message-----
From: Michael Fuhr [mailto:mike(at)fuhr(dot)org]
Sent: Friday, February 24, 2006 6:13 PM
To: Lane Van Ingen
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] pgStatTuple

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Dayo Johnson 2006-02-27 13:40:13 Re: Priviliges and Roles
Previous Message CaT 2006-02-27 12:22:50 Re: Priviliges and Roles