On Tue, Nov 8, 2022 at 6:11 PM Karthik Jagadish (kjagadis)
<kjagadis@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.
Yeswe do perform a lot of updates on that particular table which is not vacuuming. Does it mean that it waiting for the
lockto 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 <sulamul@gmail.com>
> Date: Tuesday, 8 November 2022 at 5:38 PM
> To: Karthik Jagadish (kjagadis) <kjagadis@cisco.com>
> Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>, Prasanna Satyanarayanan (prassaty)
<prassaty@cisco.com>,Chandruganth Ayyavoo Selvam (chaayyav) <chaayyav@cisco.com>, Jaganbabu M (jmunusam)
<jmunusam@cisco.com>
> Subject: Re: Tables not getting vacuumed in postgres
>
> On Tue, Nov 8, 2022 at 5:00 PM Karthik Jagadish (kjagadis)
> <kjagadis@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
happeningfor 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
