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 890CA9DC9D3 for ; Mon, 27 Feb 2006 09:28:10 -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 23023-06 for ; Mon, 27 Feb 2006 09:28:13 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from twmail.ESNCC.COM (static-66-173-159-28.t1.cavtel.net [66.173.159.28]) by postgresql.org (Postfix) with SMTP id 39FC89DC80C for ; Mon, 27 Feb 2006 09:28:07 -0400 (AST) Received: from spawar2i8uvlb9 ([150.125.117.63]) by twmail.ESNCC.COM with Microsoft SMTPSVC(6.0.3790.1830); Mon, 27 Feb 2006 08:28:11 -0500 From: "Lane Van Ingen" To: "Michael Fuhr" Cc: Subject: Re: pgStatTuple Date: Mon, 27 Feb 2006 08:31:45 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Importance: Normal In-Reply-To: <20060224231310.GA31534@winnie.fuhr.org> X-OriginalArrivalTime: 27 Feb 2006 13:28:11.0472 (UTC) FILETIME=[A7A06D00:01C63BA1] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.169 required=5 tests=[AWL=0.169] X-Spam-Score: 0.169 X-Spam-Level: X-Archive-Number: 200602/318 X-Sequence-Number: 20739 No, I didn't see the README file. Thanks so much for the info, Michael! -----Original Message----- From: Michael Fuhr [mailto:mike@fuhr.org] Sent: Friday, February 24, 2006 6:13 PM To: Lane Van Ingen Cc: pgsql-admin@postgresql.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