From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL historical database |
Date: | 2024-11-15 22:51:26 |
Message-ID: | CANzqJaBd6ij80vJVZmDzVPGHdin=5F08bxjFeNjR93ocw9uzhQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Nov 5, 2024 at 1:15 PM Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com>
wrote:
[snip]
> I would first recommend looking into partitioning for managing data
> retention like this. As Ron says, you'll want to look into the performance
> implications of this, but it allows for the most efficient method of
> removing old data from PostgreSQL and is typically worth the overhead
> costs. Otherwise you're dealing with potentially expensive deletion
> operations and managing bloat vs just detaching/dropping a table.
>
Am I the only person to have ever gotten good DELETE performance from
Postgresql?
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
From | Date | Subject | |
---|---|---|---|
Next Message | Rui DeSousa | 2024-11-15 22:51:58 | Re: PostgreSQL historical database |
Previous Message | msalais | 2024-11-15 21:58:31 | RE: PostgreSQL historical database |