---
title: "Discussion on \"The Hidden Killer of PostgreSQL Performance: Understanding and Eliminating Bloat\" | Hashnode"
description: "Discussion on \"The Hidden Killer of PostgreSQL Performance: Understanding and Eliminating Bloat\". In PostgreSQL, every UPDATE or DELETE creates dead tuples. These are old row versions that are no longer visible to any active transaction. They remain in the table and indexes until PostgreSQL’s clea"
url: "https://hashnode.com/posts/the-hidden-killer-of-postgresql-performance-understanding-and-eliminating-bloat/69c39df18a263e79cb0cca5d"
---

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

Discussion

# [The Hidden Killer of PostgreSQL Performance: Understanding and Eliminating Bloat](https://merouanballout.hashnode.dev/the-hidden-killer-of-postgresql-performance-understanding-and-eliminating-bloat?utm_source=hashnode&utm_medium=feed)

In PostgreSQL, every UPDATE or DELETE creates dead tuples. These are old row versions that are no longer visible to any active transaction. They remain in the table and indexes until PostgreSQL’s clea

Mar 25 · 4 min read · merouanballout.hashnode.dev  
Updated Mar 29  
Read the article

-   [#performance-bloat](https://hashnode.com/tag/performance-bloat)
-   [#postgresql-performance](https://hashnode.com/tag/postgresql-performance)
-   [#postgresql](https://hashnode.com/tag/postgresql)

## Written by

[Merouan Ballout](https://hashnode.com/@merouanballout)

@merouanballout · Casablanca,Morocco

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

Database Administrator & Advocate Linux & Open Source

Database Administrator and Linux System Engineer with a strong background in managing critical production environments. My expertise spans across Oracle and PostgreSQL databases, along with deep hands-on experience in Linux and UNIX systems (AIX).

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
