public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Kouber Saparev <[email protected]>
Cc: [email protected]
Subject: Re: Indexes documentation bug
Date: Mon, 04 Apr 2022 10:01:31 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAN4RuQv-nVDGLEu3J19CLWBUTf-HHB=Vsf=YL=LVvXbc06cCTw@mail.gmail.com>
References: <CAN4RuQv-nVDGLEu3J19CLWBUTf-HHB=Vsf=YL=LVvXbc06cCTw@mail.gmail.com>

Kouber Saparev <[email protected]> writes:
> 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.

Um ... you did notice that the mentions of idx_tup_fetch apply to two
different views, pg_stat_all_tables vs pg_stat_all_indexes?

			regards, tom lane

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Indexes documentation bug
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox