pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: 14n101@skct.edu.in
Subject: BUG #16421: Table Rapid Growth due to tuple accumulation
Date: Thu, 07 May 2020 11:17:30 +0000
Message-ID: <16421-540ea8a66500873d@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16421
Logged by:          basithmsk
Email address:      14n101@skct.edu.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?



Message-ID: <16421-540ea8a66500873d@postgresql.org>
Permalink:  ../16421-540ea8a66500873d@postgresql.org/
Also on:    postgresql.org/message-id/16421-540ea8a66500873d@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, 14n101@skct.edu.in
  Subject: Re: BUG #16421: Table Rapid Growth due to tuple accumulation
  In-Reply-To: <16421-540ea8a66500873d@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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