Bloated pg_catalog.pg_largeobjects - Mailing list pgsql-general

From postgresql@thewickedtribe.net
Subject Bloated pg_catalog.pg_largeobjects
Date
Msg-id 01010190d2526ef9-5d0a93fe-30ad-4d6b-9bc8-269c188bd42e-000000@us-west-2.amazonses.com
Whole thread Raw
Responses Re: Bloated pg_catalog.pg_largeobjects
Re: Bloated pg_catalog.pg_largeobjects
List 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

pgsql-general by date:

Previous
From: Michael Nolan
Date:
Subject: Re: Re. Select with where condition times out
Next
From: Priancka Chatz
Date:
Subject: Re: Bloated pg_catalog.pg_largeobjects