| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | diptatapa(at)gmail(dot)com |
| Subject: | BUG #17399: Dead tuple number stats not updated on long running queries |
| Date: | 2022-02-08 01:40:32 |
| Message-ID: | 17399-3dde82c18cf8e957@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17399
Logged by: Soni
Email address: diptatapa(at)gmail(dot)com
PostgreSQL version: 13.5
Operating system: Red Hat Enterprise Linux release 8.5 (Ootpa)
Description:
Hello All,
I think I found a bug.
While there are long running queries, a vacuum that start and end during the
long running queries, the stats of pg_stat_user_tables.n_dead_tup not
updated. The real dead tuple on the table is cleaned up, but not the
stats.
So, if dead tuple percentage on pg_stat_user_tables is above
autovacuum_vacuum_scale_factor, then the autovacuum keeps triggered during
the long running queries.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2022-02-08 07:56:24 | Re: PSQL Client command line password leak when using Connection String |
| Previous Message | Tom Lane | 2022-02-08 00:30:35 | Re: BUG #17391: While using --with-ssl=openssl and PG_TEST_EXTRA='ssl' options, SSL tests fail on OpenBSD 7.0 |