public inbox for [email protected]  

help / color / mirror / Atom feed

Indexes documentation bug
3+ messages / 2 participants
[nested] [flat]

* Indexes documentation bug
@ 2022-04-04 12:21  Kouber Saparev <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Kouber Saparev @ 2022-04-04 12:21 UTC (permalink / raw)
  To: [email protected]

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


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Indexes documentation bug
@ 2022-04-04 14:01  Tom Lane <[email protected]>
  parent: Kouber Saparev <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2022-04-04 14:01 UTC (permalink / raw)
  To: Kouber Saparev <[email protected]>; +Cc: [email protected]

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





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Indexes documentation bug
@ 2022-04-04 14:11  Kouber Saparev <[email protected]>
  parent: Tom Lane <[email protected]>
  0 siblings, 0 replies; 3+ messages in thread

From: Kouber Saparev @ 2022-04-04 14:11 UTC (permalink / raw)
  To: Tom Lane <[email protected]>; +Cc: [email protected]

My bad, yes indeed, the view is different.

На пн, 4.04.2022 г. в 17:01 ч. Tom Lane <[email protected]> написа:

> 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
>


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

end of thread, other threads:[~2022-04-04 14:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-04-04 12:21 Indexes documentation bug Kouber Saparev <[email protected]>
2022-04-04 14:01 ` Tom Lane <[email protected]>
2022-04-04 14:11   ` Kouber Saparev <[email protected]>

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