Indexes documentation bug

From: Kouber Saparev <kouber(at)gmail(dot)com>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Indexes documentation bug
Date: 2022-04-04 12:21:24
Message-ID: CAN4RuQv-nVDGLEu3J19CLWBUTf-HHB=Vsf=YL=LVvXbc06cCTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hello,

I believe there is an error within this sentence in section
https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-USER-FUNCTIONS-VIEW

"Therefore, a bitmap scan increments the
pg_stat_all_indexes.idx_tup_read count(s)
for the index(es) it uses, and it increments the pg_stat_all_tables.
idx_tup_fetch count for the table, but it does not affect
pg_stat_all_indexes.idx_tup_fetch."

There is repeated mentioning of pg_stat_all_indexes.idx_tup_fetch while I
suppose one should read pg_stat_all_indexes.idx_scan instead the second
time. I.e. bitmap scans do not increment idx_scan.

Regards,
--
Kouber Saparev

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2022-04-04 14:01:31 Re: Indexes documentation bug
Previous Message PG Doc comments form 2022-03-31 01:14:49 The ltree example could lead to misunderstandings on usage of the ltree type