From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Sebastian Böhm <seb(at)exse(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: tup_returned/ tup_fetched |
Date: | 2008-12-15 03:28:21 |
Message-ID: | 873agqqfqi.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sebastian Böhm <seb(at)exse(dot)net> writes:
> one question:
>
> what actually is tup_returned and tup_fetched ?
RTFM -- admittedly it's not so easy to find these since you have to know they
come from the following functions:
pg_stat_get_tuples_returned(oid) bigint Number of rows read by sequential
scans when argument is a table, or number of index entries returned when
argument is an index
pg_stat_get_tuples_fetched(oid) bigint Number of table rows fetched by bitmap
scans when argument is a table, or table rows fetched by simple index scans
using the index when argument is an index
From:
http://www.postgresql.org/docs/8.3/interactive/monitoring-stats.html
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!
From | Date | Subject | |
---|---|---|---|
Next Message | SunWuKung | 2008-12-15 07:50:45 | Re: application readable error message |
Previous Message | Sebastian Böhm | 2008-12-15 03:02:02 | tup_returned/ tup_fetched |