Re: more detailed description of tup_returned and tup_fetched
Masahiro Ikeda <ikedamsh@oss.nttdata.com>
From: Masahiro Ikeda <ikedamsh@oss.nttdata.com>
To: Fujii Masao <masao.fujii@oss.nttdata.com>, pgsql-docs@lists.postgresql.org
Date: 2021-05-20T08:38:44Z
Lists: pgsql-docs
Attachments
- v1-0002-add-more-detailed-description-of-tup_returned-and-tup_fetched.patch (text/x-patch) patch v1-0002
On 2021/05/20 17:00, Fujii Masao wrote: > On 2021/05/20 9:46, Masahiro Ikeda wrote: >> On 2021/05/18 20:10, Fujii Masao wrote: >>>>> pg_stat_database.tup_fetched: >>>>> Number of index entries returned by scans on indexes in this database >>>> Is this the sum of pg_stat_all_indexes.idx_tup_read? This is accounted to >>>> pg_stat_database.tup_returned. >>> >>> I was thinking that pg_stat_database.tup_fetched is the same as >>> the sum of pg_stat_all_tables.idx_tup_fetch. Because they both >>> are incremented by bitmap index scans, but pg_stat_all_indexes.idx_tup_read >>> is not. >> >> Yes. So, "Number of index entries returned by scans on indexes in this >> database" is incorrect, and "Number of live rows fetched by index scans in >> this database" is correct? > > Yes, I think so! Thanks! I updated the patch for summarizing this thread. Regards, -- Masahiro Ikeda NTT DATA CORPORATION
Commits
-
doc: Improve descriptions of tup_returned and tup_fetched in pg_stat_database
- 3465c8a8692f 15.0 landed