From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | 14n101(at)skct(dot)edu(dot)in |
Subject: | BUG #16421: Table Rapid Growth due to tuple accumulation |
Date: | 2020-05-07 11:17:30 |
Message-ID: | 16421-540ea8a66500873d@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: 16421
Logged by: basithmsk
Email address: 14n101(at)skct(dot)edu(dot)in
PostgreSQL version: 10.10
Operating system: Windows
Description:
We have a table with around 20,000 rows and it is updated very often in the
product. Autovacuum seems to be running often for this table and we've
scheduled vacuum to run for this table to be run alone once in every day
using command "VACUUM ANALYZE ". Even with this, we tend to see that the
dead tuples and live tuples of this table alone seems to grow at an
exponential rate (table size reaches nearly 25GB in 10 days). The table's
original size is around 100MB only (Ran VACUUM FULL ANALYZE on the table).
As a result of this, the table's performance becomes affected badly. The
pgsql data folder has been excluded in our AntiVirus (Deep Security agent)
as well. Can I get some help on resolving this issue?
From | Date | Subject | |
---|---|---|---|
Next Message | دار الآثار للنشر والتوزيع-صنعاء Dar Alathar-Yemen | 2020-05-07 11:48:40 | رد: BUG #16419: wrong parsing BC year in to_date() function |
Previous Message | دار الآثار للنشر والتوزيع-صنعاء Dar Alathar-Yemen | 2020-05-07 10:23:35 | رد: BUG #16419: wrong parsing BC year in to_date() function |