TRUNCATE vs DELETE vs DROP: Remove Rows Fast in PostgreSQL

Tue, 16 Jun 2026 00:00:00 +0000

TRUNCATE vs DELETE vs DROP: Remove Rows Fast in PostgreSQL

Where DELETE removes rows one logical version at a time and leaves the cleanup to vacuum, TRUNCATE discards an entire table's contents almost instantly and reclaims the space immediately, and DROP removes the table itself. Picking the wrong one for "empty this table" is a common cause of surprise WAL floods and runaway bloat.

Purpose and Overview

"Just clear the table" sounds like one operation, but PostgreSQL offers three commands with very different costs. The reason the choice matters comes down to how PostgreSQL stores data. Under multiversion concurrency control (MVCC), a DELETE does not physically remove a row — it marks each row version as deleted by stamping its xmax, leaving a dead tuple behind. Those dead tuples occupy space until vacuum reclaims them, and on a full-table delete that means writing one WAL record per row and generating dead tuples across the entire table.

Delete on Postgres Scripts

TRUNCATE vs DELETE vs DROP: Remove Rows Fast in PostgreSQL

TRUNCATE vs DELETE vs DROP: Remove Rows Fast in PostgreSQL

Purpose and Overview