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 1uNXdW-0046ki-OI for pgsql-general@arkaria.postgresql.org; Fri, 06 Jun 2025 14:01:34 +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 1uNXdU-00Arib-R7 for pgsql-general@arkaria.postgresql.org; Fri, 06 Jun 2025 14:01:33 +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 1uNXdU-00AriT-Gx for pgsql-general@lists.postgresql.org; Fri, 06 Jun 2025 14:01:33 +0000 Received: from mail-oo1-xc32.google.com ([2607:f8b0:4864:20::c32]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uNXdT-000aNV-1c for pgsql-general@postgresql.org; Fri, 06 Jun 2025 14:01:32 +0000 Received: by mail-oo1-xc32.google.com with SMTP id 006d021491bc7-6063462098eso1300952eaf.0 for ; Fri, 06 Jun 2025 07:01:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749218491; x=1749823291; 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=2HOwNKYJCWt5NqdQ9D9BXDLx1s6AZ1lQ2dr5wthkzTk=; b=MpoKuXMcweA/+abAMPdECNhrzaV80LgJqCeo4A5TDqmHEQbF8FCeWejCTe7bbJobBR ncWWGskErmqQDvw0t3FYmS00Uq5DzxdnfW2O67DbORoLqleDF5AZT6o4FBwbdIsraY5L g2TPuJcc+kwsuRpwtHs0y/6svYBGbxHIeiWDQR5mTdGUTYTnjqM3E9s7BOXccKPbOdvs y/eVCSoZnL2cpVRfG7hgCpK/IrDbxcI8odYRzabcPbh34dgtPUvOms/O54wTbGu142D4 CWwbcfAElYZ7j2VubDb+m9dzJYSw4+uszYuP7bZf6aCc+ewaysETGaEZyYNm3BpDM4t6 i4ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749218491; x=1749823291; 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=2HOwNKYJCWt5NqdQ9D9BXDLx1s6AZ1lQ2dr5wthkzTk=; b=I00eJ4TiIDkoyzojPrDQmhQsrcU8QjX+8ZqzTh9cKfuIxE2gVIGI4pNRW6ZJky+2EB U8gLOisgfhmWvKKjj8ykWVr5LOi2pN4VyFCI9HMdhqNeqwyRBj26vBgBtlBFGZNhOwcG DSDjLUp8uDR/g3RYOlFSFMtpKZyXiB/UWHd/vxWNIWrwMF5upd4rrRb0QXt7158MtJb/ I3mXH1MInhVs1lpJWLPRdZZK9pF+5uTcvQ4U/v8M49Not8Blu48McLcI1y+v+rge5UJG X7snfe56hfb63ynaLX3Yo9EarINMYPQspFbbYHS+zW8ue0o9q6Iwjho9Nq85Lgi4XU39 rY3Q== X-Gm-Message-State: AOJu0YxhxcFrGKnR6pWr1ri41YDlsVXDcHROY7yr7otZoHSsoFsHkq1U e1jJiwEdr0FUgDZQ50qU5HOgW4FEvzoNXUGuLVpP9pKMQF3RJm1h3oip4oqn+ngT6y0TT3/Ri52 Vrjfzx8bhxNqJscDb5akbRyyz7zn7S8OThg== X-Gm-Gg: ASbGncs5KV3n2T+0xfhf4kWfTbZdVRx4n1lFYffM4SuGgzIhcHJ7NC63X0d6tnwOb0H XUIv0TOobb3zbDb79/YMttVTdS8dsiGmdVkbsGEARQjE/OhL8iptxu5wYa4pOpw/RuCpsmFCdOM Rll4J0l6rBQouteHdWpJPHepayg0EHmWrhhSaLvnRngG6xD7k1vGpDpUQ= X-Google-Smtp-Source: AGHT+IGfmhp6+eNy7zlrXq+9zBkmALUUvZXhp2/zl+EJWyWS0i9lEuhbRbTvQMofANHZ2evafzMjOwwxIFSQ4Q6hy9k= X-Received: by 2002:a05:6871:4b06:b0:2e9:1143:584e with SMTP id 586e51a60fabf-2ea01590587mr1852850fac.39.1749218490420; Fri, 06 Jun 2025 07:01:30 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Fri, 6 Jun 2025 10:01:19 -0400 X-Gm-Features: AX0GCFuiiAIjdlaQFHuwi0ZRvQ3Y00_o67qdWzVrfCfHwkXonqKX6skk6wDx0Bk Message-ID: Subject: Re: Regarding fillfactor use case for only delete ops To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000c199730636e7aa7f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c199730636e7aa7f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 6, 2025 at 4:36=E2=80=AFAM Durgamahesh Manne wrote: > Hi Team > > 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 table= s > 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 table= s > This confuses me. It seems that you are deleting old data instead of just dropping the old partitions. What did I misunderstand? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000c199730636e7aa7f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Jun 6, 2025 at 4:36=E2=80=AFAM Du= rgamahesh Manne <maheshpost= gres9@gmail.com> wrote:
Hi=C2=A0 Team

Can we generate a fill factor for tables= that have delete ops ?

Does the fill factor reall= y work and help to minimize the bloat for tables that have delete ops?

I have parent table with weekly partitions So for ever= y week 50 to 60 gb of bloat generates and autovacuum params already in plac= e for child tables=C2=A0

This c= onfuses me.=C2=A0 It seems that you are deleting old data instead of just d= ropping the old partitions.

What did I misun= derstand?

--
Death t= o <Redacted>, and butter sauce.
Don't boil me, I'm still = alive.
<Redacted> lobster!
=
--000000000000c199730636e7aa7f--