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 1uNXbX-00462E-45 for pgsql-general@arkaria.postgresql.org; Fri, 06 Jun 2025 13:59:31 +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 1uNXbV-00AnUU-5Y for pgsql-general@arkaria.postgresql.org; Fri, 06 Jun 2025 13:59:29 +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 1uNXbU-00AnUL-RG for pgsql-general@lists.postgresql.org; Fri, 06 Jun 2025 13:59:29 +0000 Received: from mail-ot1-x32c.google.com ([2607:f8b0:4864:20::32c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uNXbS-000aMd-16 for pgsql-general@lists.postgresql.org; Fri, 06 Jun 2025 13:59:28 +0000 Received: by mail-ot1-x32c.google.com with SMTP id 46e09a7af769-72c16e658f4so1274290a34.1 for ; Fri, 06 Jun 2025 06:59:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749218365; x=1749823165; 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=c8lHr7fWSp0HfQJNy/oNzMBuixI1/T+jJU5uoZ4nrs4=; b=LlTSFxBaVBS5SsVtv6MUJ7t/IYNV6t2VJvWhfhWixfH9IsF4hsIq0kaWd5aKc2C848 d+c2NmHIB+CrsvpYUskiDtweOqdUkJ/mjdUovvT420/RG7okpl1pgeB1cgglzUGiqccp zI6K/dKDruKV/PWcx0JtDxf/T9WRY4ZFylXbISRLlv+j1rE++AsPCs7DoDSSB4DYoLCr khwNmDrMdkYMVXhinddBcObGQgXgu05LuDR9/nFfYi6lXTo21z+6N4R6rMC31tjTOP5j 6yvTzKaSIeK/4c66+eihbBvARXmhu5WZoPd0AZLfoo7yny74IFbxImgtwdopp3LOtfD6 Wy6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749218365; x=1749823165; 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=c8lHr7fWSp0HfQJNy/oNzMBuixI1/T+jJU5uoZ4nrs4=; b=op36EYC7W03WmwNR4zkAg2KKutMVxrOQd8+XW4AEs+jqd7Vpd1MlBVp1XvT7bC+aCT i09mPu6ylyVE0yw/HKEFBUJtShKLsx1nUlDJPlZslMmYVamNvpQhoTL6m0FHQBU7ooKJ i3UIPF6KK+9YkIGLceWsREkMq1GWDx8IaJRQRQl//CxE4vgmk8fCYbTGZ+iIvecC1xl0 2UyLotFdrbjv/SxYDGe2PuB3yZb0I7g82/icsfQL41DqVDYqnWKzC3dQlbVuYmTySWuU NVtNavky24dOHew2BuPnRchX8l8K0arT2TByzKrWje2GGeYUW5FoP8ZgL9Im8GDHW5DQ XP6g== X-Forwarded-Encrypted: i=1; AJvYcCVa81wUwrzbnQuaa3ncDGUZKL3n444tM+1upkjdVCsRKdQQoDKNo21pEPotf0ExwdXAZ3KFW870IvSPaTOm@lists.postgresql.org X-Gm-Message-State: AOJu0Yw9XLn4r4eIV244a8OuL0FTviVGFaF9cVVEBkQ20jl/PkzkC25t Y3EjMdIq2adEFOP4ZVbeLQOCFmOCAwZvU1qPSOGJq3KV8of/mTa93ufPwzbb78mJoGa813crvgf MfKeFQda7foBhu+ResVYpOCIgRkVDDdo= X-Gm-Gg: ASbGncvUFKhW52NI9QvkgQ7L6HlSQUiCmWsfRr6TgiduU59dzC2FimcY2ger2zl+u5H fUk5Fswcitp6uTKdw4F5QIU4II67DZXMjlDS2K94X5TCukWvgcTnrRseuOwknZmDX3DS7D8Afbp e8R87cTwMAtbZiO1lgCHg70ZPRxhxzlL95yLEKoin851DZ X-Google-Smtp-Source: AGHT+IE1vkYgsySX/t8bMDaIXPsBGNGxbGdU9szJwphlKmu/ZCFEg7w8L7Eb/bvo6Ql/Abu6uQPTuM600jCOPdoTWdk= X-Received: by 2002:a05:6870:17aa:b0:2e9:ea4a:8782 with SMTP id 586e51a60fabf-2ea00691960mr1911451fac.7.1749218365642; Fri, 06 Jun 2025 06:59:25 -0700 (PDT) MIME-Version: 1.0 References: <65a54f809d0339d9d6021c35f7fa14fc20a7f2e6.camel@cybertec.at> In-Reply-To: <65a54f809d0339d9d6021c35f7fa14fc20a7f2e6.camel@cybertec.at> From: Ron Johnson Date: Fri, 6 Jun 2025 09:59:14 -0400 X-Gm-Features: AX0GCFvAh4AAL8cdhUv5R77aDW6t6DUr_aWyLn-1R16a6S3y_D4XG9sYM3lWngY Message-ID: Subject: Re: Regarding fillfactor use case for only delete ops To: Laurenz Albe Cc: Durgamahesh Manne , pgsql-general Content-Type: multipart/alternative; boundary="000000000000519dd40636e7a361" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000519dd40636e7a361 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 g= b > of bloat generates and autovacuum params already in place for child table= s > > 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? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000519dd40636e7a361 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Jun 6, 2025 at 8:57=E2=80=AFAM La= urenz Albe <laurenz.albe@cyb= ertec.at> 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 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!
--000000000000519dd40636e7a361--