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

From Jim Hurne
Subject RE: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked
Date
Msg-id OF96D9805B.094F5585-ON85258593.0049A39C-85258593.0049F280@notes.na.collabserv.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>)
List pgsql-general
"Jim Hurne" <jhurne@us.ibm.com> wrote on 06/24/2020 03:44:26 PM:
> That brings us to transactions. I looked for any long-running idle
> transaction (transactions that have been idle for more than 15 or 5
> minutes), but found none.

It turns out I didn't see any long running transactions because I was
using a user who didn't have permissions to view most of the data in the
pg_stat_activity view.  When we looked using a more powerful user, we
found four transactions that had been idle for a long time. Killing those
transactions allowed vacuums to clean up the dead tuples.

This is most likely the root of all of our problems, so we can essentially
consider this mystery solved for now.

Thanks to all who gave us advice and information. It's been highly
educational. I'm just sorry it turned out to be a stupid "long running
transaction" problem. We'll know to look for that first in the future.





pgsql-general by date:

Previous
From: Paul Förster
Date:
Subject: Re: Netapp SnapCenter
Next
From: Matthias Apitz
Date:
Subject: Connecting Powerbuilder / EAserver to PostgreSQL server 11 via ODBCor JDBC