X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 426B89DCA75 for ; Fri, 24 Feb 2006 19:13:17 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 17173-04 for ; Fri, 24 Feb 2006 19:13:18 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by postgresql.org (Postfix) with ESMTP id 4DB1B9DCA20 for ; Fri, 24 Feb 2006 19:13:13 -0400 (AST) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id k1ONDBw6071255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Feb 2006 16:13:13 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.4/8.13.4) with ESMTP id k1ONDAo9078007; Fri, 24 Feb 2006 16:13:10 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.4/8.13.4/Submit) id k1ONDAgl078006; Fri, 24 Feb 2006 16:13:10 -0700 (MST) (envelope-from mfuhr) Date: Fri, 24 Feb 2006 16:13:10 -0700 From: Michael Fuhr To: Lane Van Ingen Cc: pgsql-admin@postgresql.org Subject: Re: pgStatTuple Message-ID: <20060224231310.GA31534@winnie.fuhr.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.122 required=5 tests=[AWL=0.122] X-Spam-Score: 0.122 X-Spam-Level: X-Archive-Number: 200602/310 X-Sequence-Number: 20731 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