Bloated pg_catalog.pg_largeobjects

From: postgresql(at)thewickedtribe(dot)net
To: pgsql-general(at)postgresql(dot)org <pgsql-general(at)postgresql(dot)org>
Subject: Bloated pg_catalog.pg_largeobjects
Date: 2024-07-20 22:45:36
Message-ID: 01010190d2526ef9-5d0a93fe-30ad-4d6b-9bc8-269c188bd42e-000000@us-west-2.amazonses.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Priancka Chatz 2024-07-21 07:16:31 Re: Bloated pg_catalog.pg_largeobjects
Previous Message Michael Nolan 2024-07-20 19:21:56 Re: Re. Select with where condition times out