Re: Effects of dropping a large table

From: Gus Spier <gus(dot)spier(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Effects of dropping a large table
Date: 2023-07-23 10:09:03
Message-ID: CAG8xnidWNPmc4e1W13dzm9ByR3HDEekn8Jv39vhMNSBmx8YJmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ah! Truncating a table does not entail all of WAL processes. From the
documentation, "TRUNCATE quickly removes all rows from a set of tables. It
has the same effect as an unqualified DELETE on each table, but since it
does not actually scan the tables it is faster. Furthermore, it reclaims
disk space immediately, rather than requiring a subsequent VACUUM operation.
This is most useful on large tables."
https://www.postgresql.org/docs/14/sql-truncate.html

Regards,
Gus

On Sun, Jul 23, 2023 at 5:51 AM Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:

> On 2023-07-22 16:37:39 -0400, Gus Spier wrote:
> > Isn’t this a perfect opportunity to use the TRUNCATE command to
> > quickly remove the data? And follow up by deleting the now empty
> > tables?
>
> What's the advantage of first truncating and then deleting a table over
> just deleting it?
>
> hp
>
> --
> _ | Peter J. Holzer | Story must make more sense than reality.
> |_|_) | |
> | | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
> __/ | http://www.hjp.at/ | challenge!"
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2023-07-23 10:27:33 Re: Effects of dropping a large table
Previous Message Peter J. Holzer 2023-07-23 09:51:38 Re: Effects of dropping a large table