From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Effects of dropping a large table
Date: Sun, 23 Jul 2023 15:05:30 -0500
Message-ID: <f1815a29-4ef4-bb25-0c20-d3973bf7bb2b@gmail.com> (raw)
In-Reply-To: <20230723102733.shfvgs6dsev2l6xa@hjp.at>
References: <c9fea9c6-807c-474f-d698-968d3ac2a901@gmail.com>
<430335C4-3803-4F88-9042-96BA65166043@gmail.com>
<20230723095138.vrlw4jlbafy6iktn@hjp.at>
<CAG8xnidWNPmc4e1W13dzm9ByR3HDEekn8Jv39vhMNSBmx8YJmw@mail.gmail.com>
<20230723102733.shfvgs6dsev2l6xa@hjp.at>
On 7/23/23 05:27, Peter J. Holzer wrote:
> On 2023-07-23 06:09:03 -0400, Gus Spier wrote:
>> 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
> I assumed that by "deleting the now empty table" you meant DROPing it.
> (Performing a «DELETE FROM t» just after a «TRUNCATE t» would obviously
> be pointless).
>
> So let me rephrase the question:
>
> What's the advantage of
>
> TRUNCATE t
> DROP t
>
> over just
>
> DROP t
Catalog or serialization locking? (I don't know; just asking.)
--
Born in Arizona, moved to Babylonia.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: Effects of dropping a large table
In-Reply-To: <f1815a29-4ef4-bb25-0c20-d3973bf7bb2b@gmail.com>
References: <c9fea9c6-807c-474f-d698-968d3ac2a901@gmail.com> <430335C4-3803-4F88-9042-96BA65166043@gmail.com> <20230723095138.vrlw4jlbafy6iktn@hjp.at> <CAG8xnidWNPmc4e1W13dzm9ByR3HDEekn8Jv39vhMNSBmx8YJmw@mail.gmail.com> <20230723102733.shfvgs6dsev2l6xa@hjp.at> <f1815a29-4ef4-bb25-0c20-d3973bf7bb2b@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox