Re: more detailed description of tup_returned and tup_fetched - Mailing list pgsql-docs

From Fujii Masao
Subject Re: more detailed description of tup_returned and tup_fetched
Date
Msg-id d1f01107-4fa2-381e-b81c-e064a8be9c07@oss.nttdata.com
Whole thread Raw
In response to Re: more detailed description of tup_returned and tup_fetched  (Masahiro Ikeda <ikedamsh@oss.nttdata.com>)
Responses Re: more detailed description of tup_returned and tup_fetched  (Masahiro Ikeda <ikedamsh@oss.nttdata.com>)
List pgsql-docs

On 2021/05/20 17:38, Masahiro Ikeda wrote:
> 
> 
> 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.

Thanks for updating the patch! LGTM.

This is an improvement of documentation, so this should be applied in
v15 dev cycle? If so, could you add the patch to the next CF? Or you think
this is a bug fix and needs to be back-patched?

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



pgsql-docs by date:

Previous
From: PG Doc comments form
Date:
Subject: ALTER COLLATION ... REFRESH VERSION - sample script outdated
Next
From: Pavel Luzanov
Date:
Subject: Re: pg_monitor role description