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

From: "Jim Hurne" <jhurne(at)us(dot)ibm(dot)com>
To: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
Cc: "PostgreSQL General" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: RE: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked
Date: 2020-06-24 14:24:29
Message-ID: OFB99C007D.CA15CC8E-ON85258591.004ECAD1-85258591.004F258D@notes.na.collabserv.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Daniel Verite" <daniel(at)manitou-mail(dot)org> wrote on 06/24/2020 10:08:27 AM:
> Unfortunately it [pg_repack] can't work with pg_largeobject

That is unfortunate, and potentially leaves us in a difficult spot.

Is it possible to configure PosgreSQL to use a user table for large
objects instead of a system table?

We're finding it to be especially difficult to maintain the pg_largeobject
system table (tweak autovacuum settings, manually cleanup with something
like pg_repack, etc), particularly since our PosrgreSQL instances are
hosted and controlled by another team.

Regards,

Jim Hurne

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2020-06-24 15:17:20 Re: pgbench and timestamps
Previous Message Tom Lane 2020-06-24 14:15:23 Re: pgbench and timestamps