Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tC5AJ-00AzXz-Vf for pgsql-admin@arkaria.postgresql.org; Fri, 15 Nov 2024 22:51:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tC5AH-00C5yq-BT for pgsql-admin@arkaria.postgresql.org; Fri, 15 Nov 2024 22:51:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tC5AG-00C5yh-W2 for pgsql-admin@lists.postgresql.org; Fri, 15 Nov 2024 22:51:45 +0000 Received: from mail-ot1-x336.google.com ([2607:f8b0:4864:20::336]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tC5AB-00267Z-4l for pgsql-admin@postgresql.org; Fri, 15 Nov 2024 22:51:44 +0000 Received: by mail-ot1-x336.google.com with SMTP id 46e09a7af769-718119fc061so22857a34.2 for ; Fri, 15 Nov 2024 14:51:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731711098; x=1732315898; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=i3MYD6Fm3W452bwBagLeDywu1t6nb/hKBtbeI2JZJ9w=; b=SHn1zmgvBdv953FgtOJjBuoZS/+jmmtaGRHSU3HjcIAspUCnjVrWvZ40kSKE9i+qfd X8p0GAqzNsk5BqVd9Ae/WRP2/wROj9v06mB3LqlBfo592wyHVWOyV20Av/JpXArCDlTD qjmHGBwXnaH1K/KZI+uF/2SMK56SnLsvA0znhEgZVYZneBzGOdSna5SbVCcjq/CHSRt9 nwtwzr/TL2WuJjwnjE1jg2Rgt4qa46bo7C1zeF694AnWmw7bcwGwx8Pv9HGS8lGinSaK T3ipLlVfhWk1YWacjGp1PFXq0SW5a4e1+/ZGVGwawa2V5qCd7jbBDER7MIpFEfcWc5+4 Uu2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731711098; x=1732315898; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=i3MYD6Fm3W452bwBagLeDywu1t6nb/hKBtbeI2JZJ9w=; b=pBeOfrzh+JgTngdAkQURZFNnELYQjG7VgVG4DqJ8zmxWp6ZV8/JchmAIoTQg5pWdL6 ycCKiN4QD4qsNNltqUJjM8E6wKzJEmdMELP1RTkUOhP66LHq77nj/SgwWSEn5Ic9QevP Xm4UJZVsOBJq3wSQERSDwyckMt0CYP9Do3JwTFda6mOclk3fR2GoR8pXIYs+VSbfruhP z+gAU0RNJBTxanktH0nkgIPTwL1gkyd4IZePK4lNsspY88E4L4jZJJTMoqQHPtequCnH fBDenIbK1NTpFgSd1y3gq1sVoRf1M/4O2GK3RhOK4Q3DuTMp5ouFhkuGIBW/dyrvyjq2 MLYw== X-Gm-Message-State: AOJu0Yy1HjDdG1ZGz9SCQP8NtsxS5J1swDU3nWdnjrhMK96xQR1oMdSD SIKdWJDl0zAbwmkAW3dN35+QWg6fUiVbV7Z7Iy+DhB14RCBdXDSXa4GmVvKjua5oDM5ffsoGfJG TgbSdLkqY2STRDfXrlS1z872GeEi31Q== X-Google-Smtp-Source: AGHT+IH26mtS01etmDwjmvJDnxGooiluOXKiC/zBYPh1KpJLR0MaUZkMFVMTcGqNk1/sQR0Czv4wmLqvDuN5koz9qGY= X-Received: by 2002:a05:6830:6215:b0:718:5b0f:fd47 with SMTP id 46e09a7af769-71a77a580fbmr4555081a34.25.1731711098087; Fri, 15 Nov 2024 14:51:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Fri, 15 Nov 2024 17:51:26 -0500 Message-ID: Subject: Re: PostgreSQL historical database To: pgsql-admin Content-Type: multipart/alternative; boundary="000000000000daf87e0626fb68fe" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000daf87e0626fb68fe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Nov 5, 2024 at 1:15=E2=80=AFPM Keith Fiske 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 performanc= e > 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? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000daf87e0626fb68fe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Nov 5, 2024 at 1:15=E2=80=AFPM Ke= ith Fiske <keith.fiske@cr= unchydata.com> wrote:
[snip]=C2= =A0
I would first recommend looking into partitioning for managing = data retention like this. As Ron says, you'll want to look into the per= formance implications of this, but it allows for the most efficient method = of removing old data from PostgreSQL and is typically worth the overhead co= sts. Otherwise you're dealing with potentially expensive deletion opera= tions and managing bloat vs just detaching/dropping a table.
=C2=A0
Am I the only person to have ever gotten go= od DELETE performance from Postgresql?

--
Death to <Redacted>, and butter sauce.
Don&= #39;t boil me, I'm still alive.
<Redacted> lobster!<= /div>
--000000000000daf87e0626fb68fe--