Re: Bloated pg_catalog.pg_largeobjects

[Priancka Chatz <pc9926@xxxxxxxxx>]

You have to run vacuumlo to remove orphaned large objects. 

https://www.postgresql.org/docs/current/vacuumlo.html

Regards,

Priyanka 

On Sun, 21 Jul 2024 at 12:46 AM, <postgresql@xxxxxxxxxxxxxxxxxx> wrote:

Hello All,

I've got a cluster that's having issues with pg_catalog.pg_largeobject getting massively bloated. Vacuum is running OK and there's 700GB of free space in the table and only 100GB of data, but subsequent inserts seem to be not using space from the FSM and instead always allocating new pages. The table just keeps growing.

Is this a known thing, maybe something special about LOs?

Also, is the only way to recover space here a vacuum full on the table since it's a catalog table?

Thanks,

-- 
Jon Erdman (aka StuckMojo on IRC)
    PostgreSQL Zealot