Subject: Bloated pg_catalog.pg_largeobjects
From: postgresql@thewickedtribe.net
To: 
	=?UTF-8?Q?pgsql-general=40postgresql=2Eorg?= <pgsql-general@postgresql.org>
Date: Sat, 20 Jul 2024 22:45:36 +0000
Mime-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="=_fU3DaHAH6f1IHMyUdIrMY9RTBH4Ez1gBle6jPIs765U1HG1K"
References: <mail.669c3e0f.59c4.4be7fe7e6c0b49b1@storage.wm.amazon.com>
Thread-Index: AQHa2vZPQmCh66b1RASHretbYzZKCw==
Thread-Topic: Bloated pg_catalog.pg_largeobjects
Message-ID: <01010190d2526ef9-5d0a93fe-30ad-4d6b-9bc8-269c188bd42e-000000@us-west-2.amazonses.com>
Feedback-ID: ::1.us-west-2.An468LAV0jCjQDrDLvlZjeAthld7qrhZr+vow8irkvU=:AmazonSES
Archived-At: <https://www.postgresql.org/message-id/01010190d2526ef9-5d0a93fe-30ad-4d6b-9bc8-269c188bd42e-000000%40us-west-2.amazonses.com>
Precedence: bulk

This is a multi-part message in MIME format. Your mail reader does not
understand MIME message format.
--=_fU3DaHAH6f1IHMyUdIrMY9RTBH4Ez1gBle6jPIs765U1HG1K
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello All,

I've got a cluster that's having issues with pg_catalog.pg_largeobject ge=
tting massively bloated. Vacuum is running OK and there's 700GB of free s=
pace 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=3F

Also, is the only way to recover space here a vacuum full on the table si=
nce it's a catalog table=3F

Thanks,

--=C2=A0
Jon Erdman (aka StuckMojo on IRC)
=C2=A0=C2=A0=C2=A0 PostgreSQL Zealot

--=_fU3DaHAH6f1IHMyUdIrMY9RTBH4Ez1gBle6jPIs765U1HG1K
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML><html>
<head>
<meta name=3D"Generator" content=3D"Amazon WorkMail v3.1.2598.0">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">=

<title>Bloated pg_catalog.pg_largeobjects</title>
</head>
<body>
<html><head></head><body><p style=3D"margin: 0px; font-family: Arial, Tah=
oma, Helvetica, sans-serif; font-size: small;">Hello All,<br><br>I've got=
 a cluster that's having issues with pg_catalog.pg_largeobject getting ma=
ssively 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 u=
sing space from the FSM and instead always allocating new pages. The tabl=
e just keeps growing.<br><br>Is this a known thing, maybe something speci=
al about LOs=3F<br><br>Also, is the only way to recover space here a vacu=
um full on the table since it's a catalog table=3F<br><br>Thanks,</p><div=
 class=3D"moz-txt-sig"><span class=3D"moz-txt-tag">--&nbsp;</span><br>Jon=
 Erdman (aka StuckMojo on IRC)<br>&nbsp;&nbsp;&nbsp; PostgreSQL Zealot</d=
iv></body></html>
</body>
</html>
--=_fU3DaHAH6f1IHMyUdIrMY9RTBH4Ez1gBle6jPIs765U1HG1K--