public inbox for [email protected]help / color / mirror / Atom feed
Bloated pg_catalog.pg_largeobjects 4+ messages / 3 participants [nested] [flat]
* Bloated pg_catalog.pg_largeobjects @ 2024-07-20 22:45 [email protected] 2024-07-21 07:16 ` Re: Bloated pg_catalog.pg_largeobjects Priancka Chatz <[email protected]> 2024-07-22 11:21 ` Re: Bloated pg_catalog.pg_largeobjects khan Affan <[email protected]> 0 siblings, 2 replies; 4+ messages in thread From: [email protected] @ 2024-07-20 22:45 UTC (permalink / raw) To: 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 ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Bloated pg_catalog.pg_largeobjects 2024-07-20 22:45 Bloated pg_catalog.pg_largeobjects [email protected] @ 2024-07-21 07:16 ` Priancka Chatz <[email protected]> 1 sibling, 0 replies; 4+ messages in thread From: Priancka Chatz @ 2024-07-21 07:16 UTC (permalink / raw) To: [email protected]; +Cc: pgsql-general 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 > ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Bloated pg_catalog.pg_largeobjects 2024-07-20 22:45 Bloated pg_catalog.pg_largeobjects [email protected] @ 2024-07-22 11:21 ` khan Affan <[email protected]> 2024-07-22 12:03 ` Re: Bloated pg_catalog.pg_largeobjects Priancka Chatz <[email protected]> 1 sibling, 1 reply; 4+ messages in thread From: khan Affan @ 2024-07-22 11:21 UTC (permalink / raw) To: [email protected]; +Cc: pgsql-general Hi I would suggest to backup your DB before doing such a thing. Run Vaccum Full, (VACUUM FULL pg_catalog.pg_largeobject) Running this on the system table might be risky Make sure you backup the database. & if you are using PG version above 9.1 use Pg_repack to reclaim the space. Note: It can be disruptive, so planning and preparing for potential downtime is essential. Thanks & regards *Muhammad Affan (*아판*)* *PostgreSQL Technical Support Engineer** / Pakistan R&D* Interlace Plaza 4th floor Twinhub office 32 I8 Markaz, Islamabad, Pakistan On Sun, Jul 21, 2024 at 3: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 > ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Bloated pg_catalog.pg_largeobjects 2024-07-20 22:45 Bloated pg_catalog.pg_largeobjects [email protected] 2024-07-22 11:21 ` Re: Bloated pg_catalog.pg_largeobjects khan Affan <[email protected]> @ 2024-07-22 12:03 ` Priancka Chatz <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Priancka Chatz @ 2024-07-22 12:03 UTC (permalink / raw) To: khan Affan <[email protected]>; +Cc: [email protected]; pgsql-general Vacuum Full will not help here if you have large objects present in the pg_largeobjects table but not being referred to by any table. Vacuumlo doesn't require downtime but based on the data it needs to remove can run long and use resources and hence schedule it in off peak hours. You can do a dry run to get an estimate. On Mon, Jul 22, 2024 at 1:21 PM khan Affan <[email protected]> wrote: > Hi > > I would suggest to backup your DB before doing such a thing. > > Run Vaccum Full, (VACUUM FULL pg_catalog.pg_largeobject) Running this on > the system table might be risky Make sure you backup the database. > > & if you are using PG version above 9.1 use Pg_repack to reclaim the space. > > Note: It can be disruptive, so planning and preparing for potential > downtime is essential. > > Thanks & regards > > > *Muhammad Affan (*아판*)* > > *PostgreSQL Technical Support Engineer** / Pakistan R&D* > > Interlace Plaza 4th floor Twinhub office 32 I8 Markaz, Islamabad, Pakistan > > On Sun, Jul 21, 2024 at 3: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 >> > ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2024-07-22 12:03 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-07-20 22:45 Bloated pg_catalog.pg_largeobjects [email protected] 2024-07-21 07:16 ` Priancka Chatz <[email protected]> 2024-07-22 11:21 ` khan Affan <[email protected]> 2024-07-22 12:03 ` Priancka Chatz <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox