Re: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked - Mailing list pgsql-general

From Michael Lewis
Subject Re: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked
Date
Msg-id CAHOFxGoOaVk6KPQgrijZAfrbAdkwW3jQZTjb=swOXU4dk8MidQ@mail.gmail.com
Whole thread Raw
In response to RE: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked  ("Jim Hurne" <jhurne@us.ibm.com>)
Responses Re: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked  ("Jim Hurne" <jhurne@us.ibm.com>)
List pgsql-general
On Tue, Jun 23, 2020 at 2:34 PM Jim Hurne <jhurne@us.ibm.com> wrote:
Sure! Below are more of the details from the same set of logs. Looking at
them myself, I see that there is always some percentage of tuples that are
dead but are not yet removable. And that number increases on every vacuum,
which might explain in part why autovacuum elapsed times keep increasing.

What causes a dead tuple to be unremovable?

Here are a couple good write ups.

Long running transactions are the common one that I see. You might be dealing with replication slots or prepared transactions. Basically, if some process might see that "old truth", then it can't be vacuumed away yet.

pgsql-general by date:

Previous
From: "Jim Hurne"
Date:
Subject: RE: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked
Next
From: Michael Lewis
Date:
Subject: Re: Persistent Connections