The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/explicit-locking.html
Description:
The ROW SHARE table level lock modes section currently states:
```
Conflicts with the EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
The SELECT FOR UPDATE a
My bad, yes indeed, the view is different.
На пн, 4.04.2022 г. в 17:01 ч. Tom Lane написа:
> Kouber Saparev 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
>
> > "T
Kouber Saparev 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
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 t
