public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-admin <[email protected]>
Subject: Re: PostgreSQL historical database
Date: Fri, 15 Nov 2024 17:51:26 -0500
Message-ID: <CANzqJaBd6ij80vJVZmDzVPGHdin=5F08bxjFeNjR93ocw9uzhQ@mail.gmail.com> (raw)
In-Reply-To: <CAODZiv6e4fBROiXjZ8iKEcEMrt=qUeP+vyoc5RmjKpqu8Z_THw@mail.gmail.com>
References: <CA+dvXXuiL4+SRCZ5fqTr4WZ+pHhRaC9e=D7APBcZ2JGJZMiy6w@mail.gmail.com>
<CAAo1mbnMTFf9pAyoY7dGGR5xKmZcEd6-nRZ9xyNNa3d5DoJLyg@mail.gmail.com>
<CA+dvXXvQAFm_NHKStG4P8WOxWhM6DGYLcMMM9_B02iE5gsw_bg@mail.gmail.com>
<CAODZiv6e4fBROiXjZ8iKEcEMrt=qUeP+vyoc5RmjKpqu8Z_THw@mail.gmail.com>
On Tue, Nov 5, 2024 at 1:15 PM Keith Fiske <[email protected]>
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!
view thread (11+ messages) latest in thread
reply
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 using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: PostgreSQL historical database
In-Reply-To: <CANzqJaBd6ij80vJVZmDzVPGHdin=5F08bxjFeNjR93ocw9uzhQ@mail.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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox