Sv: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Sv: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked
Date: 2020-06-16 21:19:36
Message-ID: VisenaEmail.74.9d4616d0a8a39a38.172befd99f2@tc7-visena
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general


På tirsdag 16. juni 2020 kl. 17:59:37, skrev Jim Hurne <jhurne(at)us(dot)ibm(dot)com
<mailto:jhurne(at)us(dot)ibm(dot)com>>:
We have a cloud service that uses PostgreSQL to temporarily store binary
content. We're using PostgreSQL's Large Objects to store the binary
content. Each large object lives anywhere from a few hundred milliseconds
to 5-10 minutes, after which it is deleted.
[...]

In my experience vacuumlo, https://www.postgresql.org/docs/12/vacuumlo.html
<https://www.postgresql.org/docs/12/vacuumlo.html>, is needed to remove large
objects, before vacuum can remove them from pg_largeobject.

--
Andreas Joseph Krogh

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Eugene Pazhitnov 2020-06-16 21:30:13 Re: pg_repack: WARNING: relation must have a primary key or not-null unique keys
Previous Message Michael Lewis 2020-06-16 20:41:16 Re: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked