Re: more detailed description of tup_returned and tup_fetched

From: Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: more detailed description of tup_returned and tup_fetched
Date: 2021-05-20 08:38:44
Message-ID: e50ffb9e-153f-cb1a-3e59-7edee60941cc@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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

Attachment Content-Type Size
v1-0002-add-more-detailed-description-of-tup_returned-and-tup_fetched.patch text/x-patch 956 bytes

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Julien Rouhaud 2021-05-20 08:54:27 Re: pg_monitor role description
Previous Message Fujii Masao 2021-05-20 08:00:13 Re: more detailed description of tup_returned and tup_fetched