MIME-Version: 1.0
References: <mail.669c3e0f.59c4.4be7fe7e6c0b49b1@storage.wm.amazon.com> <01010190d2526ef9-5d0a93fe-30ad-4d6b-9bc8-269c188bd42e-000000@us-west-2.amazonses.com>
In-Reply-To: <01010190d2526ef9-5d0a93fe-30ad-4d6b-9bc8-269c188bd42e-000000@us-west-2.amazonses.com>
From: Priancka Chatz <pc9926@gmail.com>
Date: Sun, 21 Jul 2024 09:16:31 +0200
Message-ID: <CANnOdgb0sJqjPxHmRuJPkJh4ig1xhDvcQBcXAm01ujUe+4L=2g@mail.gmail.com>
Subject: Re: Bloated pg_catalog.pg_largeobjects
To: postgresql@thewickedtribe.net
Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000d5af92061dbcb575"
Archived-At: <https://www.postgresql.org/message-id/CANnOdgb0sJqjPxHmRuJPkJh4ig1xhDvcQBcXAm01ujUe%2B4L%3D2g%40mail.gmail.com>
Precedence: bulk

--000000000000d5af92061dbcb575
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFAM, <postgresql@thewickedtribe.net> wr=
ote:

> 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
>

--000000000000d5af92061dbcb575
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">You have to run vacuumlo to remove orphaned large objects=
.=C2=A0</div><div dir=3D"auto"><div><a href=3D"https://www.postgresql.org/d=
ocs/current/vacuumlo.html">https://www.postgresql.org/docs/current/vacuumlo=
.html</a></div><br></div><div dir=3D"auto">Regards,</div><div dir=3D"auto">=
Priyanka=C2=A0</div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Sun, 21 Jul 2024 at 12:46=E2=80=AFAM, &lt;<a href=3D"=
mailto:postgresql@thewickedtribe.net">postgresql@thewickedtribe.net</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;bo=
rder-left-color:rgb(204,204,204)"><u></u>


<div>
<div><p style=3D"margin:0px;font-family:Arial,Tahoma,Helvetica,sans-serif;f=
ont-size:small">Hello All,<br><br>I&#39;ve got a cluster that&#39;s having =
issues with pg_catalog.pg_largeobject getting massively bloated. Vacuum is =
running OK and there&#39;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.<br><br>=
Is this a known thing, maybe something special about LOs?<br><br>Also, is t=
he only way to recover space here a vacuum full on the table since it&#39;s=
 a catalog table?<br><br>Thanks,</p></div></div><div><div><div><span>--=C2=
=A0</span><br>Jon Erdman (aka StuckMojo on IRC)<br>=C2=A0=C2=A0=C2=A0 Postg=
reSQL Zealot</div></div>
</div>
</blockquote></div></div>

--000000000000d5af92061dbcb575--