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 1uNg2l-006pe3-NN for pgsql-general@arkaria.postgresql.org; Fri, 06 Jun 2025 23:00:11 +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 1uNg2j-001xSH-PZ for pgsql-general@arkaria.postgresql.org; Fri, 06 Jun 2025 23:00:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uNg2j-001xQp-Eg for pgsql-general@lists.postgresql.org; Fri, 06 Jun 2025 23:00:10 +0000 Received: from mail-ej1-x62b.google.com ([2a00:1450:4864:20::62b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uNg2i-000cbY-1o for pgsql-general@lists.postgresql.org; Fri, 06 Jun 2025 23:00:09 +0000 Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-ade30256175so154454366b.1 for ; Fri, 06 Jun 2025 16:00:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749250807; x=1749855607; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=f4EsHeS8zCghuaMt3x6cXPhgzOcr4rg5IMTsPk0VBVg=; b=k8nus+DDXbEzjmgR7z2jFXHq8QL0zANxH3uZdRAo7lM4omaZnCvOE46Tg2UO3q+ZBy t0ErVlbGRFrfjS1NX15Hrl2WTeJvK3O7enN56hNdCGAFRxTpw6eRXSyvSyiFc7sI5hSw eS+0xWGXaFksS2MmAKomrv5ioG/oNHuqBZfp+PRYGpQTcOb14HTSX815Buvbtr9GkBT9 QGMX/ha4DrWSDPUfrF1HWYynPp+nl6X+zEb8/ta48im7i2dYkrW1aIxhKqcPA4M5Tvzw ZtclE2UxxtW3eiiMxxjWjw2sW2A7W4Cq6Q+J+CccfovAF6Zpvl3NIdd2+KYggw/U+8Sd GrUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749250807; x=1749855607; h=cc: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=f4EsHeS8zCghuaMt3x6cXPhgzOcr4rg5IMTsPk0VBVg=; b=II+APH7ia3W6HUb0++cIoX/WnUzu4CRVV3Qvjlh0Q/804NqFKI9GqqpBLaTUq2TCHx I1Ir4ycYV9WVCTy3cjL9d6NaA6p+86unoA/G/crihqvys/iW7rQw2Pu8kdU5pq2IhOVY hDpDdlzatjWuMuvRmqKL1JTL9xJNRE/3ckPdrrhOHwRVl/MI0MlJpwiybafd2Xa5PE7i 97/2QJvgpSN/um6Kooc+JuOVT6xbA1udkx4wsmLKYjOO1aN/DZo03f4xC18nNRoKgUf+ 7oPqp2S9NamE5lqMVBfYD8VnIury8aA9AaZDnuv1o8a8+V7klcSHm1G5dH/WuJZW8SmM vBOQ== X-Forwarded-Encrypted: i=1; AJvYcCVL3H1K/SbWYBmipICkQI0d8cRlS3b3/LuRprfjE39w25r79214xzA+IKl07pJlQF75Pq2s1jvC+lR2Wvx3@lists.postgresql.org X-Gm-Message-State: AOJu0Yzcyd96GriHFSUDo+qLrjN4q/5yWraGFSYDPzaLBi+tzieu+mSr SXDa/mmUWDYQ8VyEsxdLd6X6orufFtTAJ+EuPK70hZu3mCuKwojXUwl9gyP4IPHlY/scv+xv48i DhCvPX1ww1rLbXNjNceQKNa7DJ/ICdqQ= X-Gm-Gg: ASbGnctG+ImcDTAp388ChvJzT3NJ1yWo7+ScIPSO6j+u0xoy8DLn0oKyq+HxKTV4A3x Rz7HKFP6LW98e44YITcwFL0wgVUY+5pZbOxqaG2kP6RQoC+11IKf65Fa6GxBBMKrqdn4RmRt2eV K5Z6duYGxqwqqBJd5Kfs44wOAbC7HiYBMLTOWh0BbMa5A= X-Google-Smtp-Source: AGHT+IFtk1/L1l+OqYNdZAuL3xzQ3UXcTQEBKXzRytj6tQwdUayJtGY24ePs337wfBcZG056hO3Gi1+MxjIF19Vn5RU= X-Received: by 2002:a17:907:2d1e:b0:adb:335b:decb with SMTP id a640c23a62f3a-ade1a93384fmr443808266b.24.1749250806885; Fri, 06 Jun 2025 16:00:06 -0700 (PDT) MIME-Version: 1.0 References: <65a54f809d0339d9d6021c35f7fa14fc20a7f2e6.camel@cybertec.at> In-Reply-To: From: Durgamahesh Manne Date: Sat, 7 Jun 2025 04:34:21 +0530 X-Gm-Features: AX0GCFuV5eNnHRzqY3Pa0e-x-94GZ4pxk8yXN67kgAytZMTXLpLK_AWPd9hFoz8 Message-ID: Subject: Re: Regarding fillfactor use case for only delete ops To: Ron Johnson Cc: Laurenz Albe , pgsql-general Content-Type: multipart/alternative; boundary="000000000000f7af3b0636ef3091" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f7af3b0636ef3091 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 6, 2025 at 7:29=E2=80=AFPM Ron Johnson wrote: > On Fri, Jun 6, 2025 at 8:57=E2=80=AFAM Laurenz Albe > wrote: > >> On Fri, 2025-06-06 at 14:10 +0530, Durgamahesh Manne wrote: >> > Can we generate a fill factor for tables that have delete ops ? >> > >> > Does the fill factor really work and help to minimize the bloat for >> tables that have delete ops? >> > >> > I have parent table with weekly partitions So for every week 50 to 60 >> gb of bloat generates and autovacuum params already in place for child >> tables >> >> Nothing can ever avoid bloat caused by DELETE, except partitioning in a >> way that you can drop a partition rather than running DELETE. >> >> > Laurenz, > > Isn't the fill factor aimed at reducing bloat during updates of HOT table= s? > > -- > Death to , and butter sauce. > Don't boil me, I'm still alive. > lobster! > Hi I believe that fill factor works exclusively for updates of HOT tables but not for delete ops Regards, Durga Mahesh --000000000000f7af3b0636ef3091 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Jun 6, = 2025 at 7:29=E2=80=AFPM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
On Fri, = Jun 6, 2025 at 8:57=E2=80=AFAM Laurenz Albe <laurenz.albe@cybertec.at> wrote:<= /div>
On Fri, 2025-06-06 at 14:10 +0530, Durgamahesh Manne wrote:
> Can we generate a fill factor for tables that have delete ops ?
>
> Does the fill factor really work and help to minimize the bloat for ta= bles that have delete ops?
>
> I have parent table with weekly partitions So for every week 50 to 60 = gb of bloat generates and autovacuum params already in place for child tabl= es=C2=A0

Nothing can ever avoid bloat caused by DELETE, except partitioning in a
way that you can drop a partition rather than running DELETE.


Laurenz,

Isn't the = fill factor aimed at reducing bloat during updates of HOT tables?

--
Death to <Redacte= d>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!


Hi=C2=A0=C2=A0

I believe that fill factor works exclusively for updates of HOT table= s=C2=A0 but not for delete ops=C2=A0=C2=A0

Regards,
Durga = Mahesh=C2=A0

--000000000000f7af3b0636ef3091--