| From: | "maschka, sam" <sam(dot)maschka(at)nextworld(dot)net> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Autovacuum potential bug |
| Date: | 2020-01-10 21:13:47 |
| Message-ID: | CACydT65+Z_B80xnc+byYxrm0gzGW+Ko+HMxBDb+5ks0C1ctiAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
We have been seeing an issue where reads on a table seem to slowly degrade
over time. When we run VACUUM ANALYZE on the table the operations perform
much better. It usually takes about a week or two for the reads to degrade
to a point where we have to manually run VACUUM ANALYZE. This has been
happening to a handful of our tables. The mutation operations ran against
these tables are mainly update operations. Very few insert and delete
operations are ran against these tables. Also a jsonb object stores most of
the data within each record. The size of the jsonb object can vary widely
between records. We thought the autovacuum facility would have prevented us
from having to periodically run VACUUM ANALYZE. Is this a bug or is it a
configuration issue on our tables?
*Sam Maschka*
Software Engineer
651-245-4054
*ne**x**tw**o**rld* <http://www.nextworld.net/>
7979 E. Tufts Ave. Suite 900
<https://maps.google.com/?q=7979+E.+Tufts+Ave.+Suite+900+%0D+Denver,+CO+80237&entry=gmail&source=g>
Denver, CO 80237
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-01-10 22:12:31 | Re: Autovacuum potential bug |
| Previous Message | Tomas Vondra | 2020-01-10 20:28:18 | Re: BUG #16203: So difficult to set an use postgres |