On Tue, Nov 8, 2022 at 6:11 PM Karthik Jagadish (kjagadis) <kjaga...@cisco.com> wrote: > > Hi, > > > > Thanks for the response. > > > > But what I understand that insert update and delete would still work and will > not interfere with vacuuming process. Yes we do perform a lot of updates on > that particular table which is not vacuuming. Does it mean that it waiting > for the lock to be released? >
Well, yes, that won't interfere but the primary job of autovacuum is to remove the bloat, if the dead tuple(s) is visible to any transaction, then not going to remove that. > > > Regards, > > Karthik > > > > From: Amul Sul <sula...@gmail.com> > Date: Tuesday, 8 November 2022 at 5:38 PM > To: Karthik Jagadish (kjagadis) <kjaga...@cisco.com> > Cc: pgsql-hack...@postgresql.org <pgsql-hack...@postgresql.org>, Prasanna > Satyanarayanan (prassaty) <prass...@cisco.com>, Chandruganth Ayyavoo Selvam > (chaayyav) <chaay...@cisco.com>, Jaganbabu M (jmunusam) <jmunu...@cisco.com> > Subject: Re: Tables not getting vacuumed in postgres > > On Tue, Nov 8, 2022 at 5:00 PM Karthik Jagadish (kjagadis) > <kjaga...@cisco.com> wrote: > > > > Hi, > > > > We have a NMS application where we are using postgres as database, what we > > are noticing is that vacuuming is not happening for certain tables for 2-3 > > days and eventually the table bloats and disk space is running out. > > > > What could be the reason for auto vacuuming not happening for certain > > tables? > > > > Check if there is any long-running or prepared transaction. > > Regards, > Amul
