public inbox for [email protected]
help / color / mirror / Atom feedFrom: Priancka Chatz <[email protected]>
To: [email protected]
Cc: [email protected] <[email protected]>
Subject: Re: Bloated pg_catalog.pg_largeobjects
Date: Sun, 21 Jul 2024 09:16:31 +0200
Message-ID: <CANnOdgb0sJqjPxHmRuJPkJh4ig1xhDvcQBcXAm01ujUe+4L=2g@mail.gmail.com> (raw)
In-Reply-To: <01010190d2526ef9-5d0a93fe-30ad-4d6b-9bc8-269c188bd42e-000000@us-west-2.amazonses.com>
References: <[email protected]>
<01010190d2526ef9-5d0a93fe-30ad-4d6b-9bc8-269c188bd42e-000000@us-west-2.amazonses.com>
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, <[email protected]> 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
>
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Bloated pg_catalog.pg_largeobjects
In-Reply-To: <CANnOdgb0sJqjPxHmRuJPkJh4ig1xhDvcQBcXAm01ujUe+4L=2g@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox