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 1tvJFq-003LSM-Cd for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Mar 2025 17:00:26 +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 1tvJFp-004wig-3W for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Mar 2025 17:00:25 +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 1tvJFo-004wiX-QK for pgsql-hackers@lists.postgresql.org; Thu, 20 Mar 2025 17:00:24 +0000 Received: from mail-oo1-xc2f.google.com ([2607:f8b0:4864:20::c2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tvJFn-000AEF-13 for pgsql-hackers@postgresql.org; Thu, 20 Mar 2025 17:00:23 +0000 Received: by mail-oo1-xc2f.google.com with SMTP id 006d021491bc7-5fe944a4243so247720eaf.0 for ; Thu, 20 Mar 2025 10:00:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1742490022; x=1743094822; darn=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=vmrmm6bAt4lcoY6U5YfoRoNlCh1hmZGXxsjto5tz2us=; b=W+oxXVYtCkUWijPoDaBAtR+ow0f2QknFnyNBJ245Zu/ZBos0zHpPP/PeGH3QtoeN11 Y4MJxTq/Ad8BOecYaGFTZL678h19gkEfLewTE+44E6W8K7RLHk0R0+Lb3czbs+KFlDFt PIHxvQq0PY7sMroe6nYmZe10TCCQxdycFS5ewEj9kHjOFqXZqNwnrGJEez2cr4HCQMgR ovhsJJOs8AtL4zPB9q2cP+6bcvBG/YaQT7V5lvohUSG0qu41tGaCutPB196ZSdGMKSb3 Er5MD4pxsTM1WAUdWw0GP3lChXKdv/Ru6UOw4M27mBtQ9Cbvz4wq36l6YRkzndClyRqc N1Ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742490022; x=1743094822; 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=vmrmm6bAt4lcoY6U5YfoRoNlCh1hmZGXxsjto5tz2us=; b=cCvYfFQI0g9ITwYKvsAfD2CX5jx3jQQPfruLNIz/12vtmN+x7CrjDIsEcnHotnGMuq o4NGcX/JLU7KPtYBLe/p8vVdT/Ofe17RGSxg9cCriktRnFOAwH0/8s3X0kfxoWLrKd/h 8277pzCOUPHa2WQz+KAKkIWWyN/v7En90jB7Jgv+tH2Cd9hM9p1ri79YHiEFhGLLAf73 EBSh5tAKTzUBsrpUs/YwO+HCYWtkUitSaLcvlCSuSEw0lET0lE3OTiZQ4/QU67gdjUpH +cbQPrZKa871U0BIMBINv7QpoTlyBv4WfTEspMKQRdE0d+hPpH3EdJrg6JJGfp9DiPPS ZmAQ== X-Forwarded-Encrypted: i=1; AJvYcCVdh9BKOl/S7dnm/RsC8sQ40zHcz4/604RGJ7jOlttkYzHAGigZfKhvF/78F/QKSucXrLDLDBoUogxX4T8q@postgresql.org X-Gm-Message-State: AOJu0Yx325nbI9oULJ4nvueaRV+788I9st774vjsTDiCG1FWK5aMxxdZ RwWYbXXJ9kroenv1qdSwzkxb6oXI/QwilfIhLhJU34Jc4Jzps8sjdU6MSptqOytw/fA2xtdkqw0 FbeWVIkGmhDRjbDL8nvtL/dNr/ng= X-Gm-Gg: ASbGnctTUCn6QpBBBEBe57HuOv8/dG17sAaD/pJhlsfW4c6vGpkDhYzU80L082M/uSP t8M+ihUQg4yCQF1cqeTpPhbJVAw9nHCu9P37YZsGGTLzq/xiMlmsG1oENduoB7Tt8kyuiuUaePU YnpQ+yZwj4DUoIV6K0bwKtVJLQ X-Google-Smtp-Source: AGHT+IFvI2fP28BTM9pawdlYNcJz1DwmxZY1SobCwFtO8USHEgaiNLeY7y736/vf8gRrcO7cad1HeiOhQrvP9N6POhg= X-Received: by 2002:a05:6820:508b:b0:601:f716:10cf with SMTP id 006d021491bc7-6023448248bmr67475eaf.1.1742490022133; Thu, 20 Mar 2025 10:00:22 -0700 (PDT) MIME-Version: 1.0 References: <28773a66-fb88-41cf-a7ec-4216e6c91c94@oss.nttdata.com> <6f2f2167f4be09e6ca9251c8f69dfe01809d68be.camel@cybertec.at> <88e3b55a-8ef8-4b53-8d71-6bfde1a07bc1@oss.nttdata.com> In-Reply-To: From: "David G. Johnston" Date: Thu, 20 Mar 2025 09:59:45 -0700 X-Gm-Features: AQ5f1JqmALWWTPNGOIUmNYJ97tHvGCO_3boIqoKvcgcZcTp8UbNfugDUI06rQtE Message-ID: Subject: Re: Disabling vacuum truncate for autovacuum To: Nathan Bossart Cc: Fujii Masao , Robert Treat , Laurenz Albe , Gurjeet Singh , Andres Freund , Will Storey , Robert Haas , Postgres Hackers Content-Type: multipart/alternative; boundary="000000000000cb48c80630c912f5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000cb48c80630c912f5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 20, 2025 at 8:18=E2=80=AFAM Nathan Bossart wrote: > Committed. > > We added isset_offset to the public struct to introduce this new general behavior of tracking whether any table reloption has been set (not just vacuum_truncate) without any comments. I get the need for this kind of logic, since we used a boolean for the table option, but as a self-proclaimed hack it seems worth more comments than provided here. Especially pertaining to whether this is indeed generic or vacuum_truncate specific. It's unclear since both isset and vacuum_truncate_set have been introduced. If it is now a general property applying to any setting then vacuum_truncate_set shouldn't be needed - we should just get the isset value of the existing vacuum_truncate reloption by name. David J. --000000000000cb48c80630c912f5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Mar 20, 2025 at 8:18=E2=80=AFAM Nathan Bossart <= ;nathandbossart@gmail.com&g= t; wrote:
Committed.


We added isset_offset to the public struct to int= roduce this new general behavior of tracking=C2=A0whether any table relopti= on has been set (not just vacuum_truncate) without any comments.
I get the need for this kind of logic, since we used a boolean f= or the table option, but as a self-proclaimed hack it seems worth more comm= ents than provided here.=C2=A0 Especially pertaining to whether this is ind= eed generic or vacuum_truncate specific.=C2=A0 It's unclear since both = isset and vacuum_truncate_set have been introduced.=C2=A0 If it is now a ge= neral property applying to any setting then vacuum_truncate_set shouldn'= ;t be needed - we should just get the isset value of the existing vacuum_tr= uncate reloption by name.

David J.

<= /div>
--000000000000cb48c80630c912f5--