---
title: "Discussion on \"The Case of the Bloating Database: Solving the PostgreSQL Large Object Leak\" | Hashnode"
description: "Discussion on \"The Case of the Bloating Database: Solving the PostgreSQL Large Object Leak\". Unlinked Large Objects — when deleted pointers leave orphaned bytes in `pg_largeobject`"
url: "https://hashnode.com/posts/the-case-of-the-bloating-database-solving-the-postgresql-large-object-leak/6a198fe244ce1bc53eaeb39c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Case of the Bloating Database: Solving the PostgreSQL Large Object Leak](https://blog.ioop.se/the-case-of-the-bloating-database-solving-the-postgresql-large-object-leak?utm_source=hashnode&utm_medium=feed)

Unlinked Large Objects — when deleted pointers leave orphaned bytes in \`pg\_largeobject\`

May 29 · 11 min read · blog.ioop.se  
Read the article

-   [#large-objects](https://hashnode.com/tag/large-objects)
-   [#lo-unlink](https://hashnode.com/tag/lo-unlink)
-   [#vacuumlo](https://hashnode.com/tag/vacuumlo)
-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#hibernate](https://hashnode.com/tag/hibernate)

## Written by

[Magnus Karlsson](https://hashnode.com/@makarlsso)

@makarlsso · Sweden

  
[View profile](https://hashnode.com/@makarlsso)

Deciphering Systems & Strategies

Hi, I’m Magnus. I solve problems by wearing many hats—from C-suite strategy to systems-level code. 30 years in the evolution of software has taught me that the best systems live where business intent meets technical precision. Currently, I’m favoring the safety of Rust and Zig over the latencies of the JVM.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
