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 1tveih-006nii-Fs for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Mar 2025 15:55:39 +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 1tveif-00AK4O-Ux for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Mar 2025 15:55:37 +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 1tveif-00AK4G-LN for pgsql-hackers@lists.postgresql.org; Fri, 21 Mar 2025 15:55:37 +0000 Received: from mail-oo1-xc2a.google.com ([2607:f8b0:4864:20::c2a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tveid-000LRn-27 for pgsql-hackers@postgresql.org; Fri, 21 Mar 2025 15:55:37 +0000 Received: by mail-oo1-xc2a.google.com with SMTP id 006d021491bc7-601f3674116so525345eaf.2 for ; Fri, 21 Mar 2025 08:55:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1742572534; x=1743177334; 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=SpT0G8Nv5aM/BCsPUOv1HWSj1TWd9cMRKrIHmQ8XuOY=; b=T33yieQdKcaizEXHCrb/bL6474e2p8Bgd8pEkMroqluvl3PObxTPetgcHmVkOI1zWZ sZaJ7Di4RSBWMDxK9GQm5f7pEKzwb6FfsgR312GuGoNVUCemFkWJVdBviolbWvhLdlqr VTLV0y8TllwMaO+CxkRPMt3HAuMwK6Ck/U/TvT1O9WelF9DbACx2WI334P5G3JWuudGi 6vuDwl+i0hMuwBFYEUMPFlab+koG7At1iTrVOw48i3v8AxvGKv9D15wE+aw5GoTLnI/Z yBKb4XEjhsWn/RP5OypD6L8CZIflCklxFgfTPR+5asM8DvZ6yoflVSyU8EDIQrqoGqFD OGhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742572534; x=1743177334; 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=SpT0G8Nv5aM/BCsPUOv1HWSj1TWd9cMRKrIHmQ8XuOY=; b=B/N2Et7yoFhfj8YJWHnknpQooSY4q8ss60SEXvph62300gYmbB3RRYoWSyYex2CCZ+ Slbl5X1GJx+Q01DcoFBKx+sq9nlaJ+a1n1nVAyFhpT5C8iQC1gTDrzgiYpez9xIqOPb0 cxjN6IJq5bQBSwigZZ74Fnf6WFfWcZhq0QB5OXa8y3FiTpIHmeTj2DFB92Ai1A/Kc9ad gPkG7fBQmV0LR7WuIszxcO4RFIEC3/OwCqYdUJuQwsR8g6IH43BUiY7lU1CzS1YR7Yq3 kDPwEXkz3tGpZ/fU4sY9ExQ9LrUbnQBLQhKBqERYdPgakf6oqf/Oap0ZRByJ7X8+hdEO 1pSg== X-Forwarded-Encrypted: i=1; AJvYcCU3XOfoAPwV//L5eUGWrcSHn8W3fJWYPFlfIqJE+sHothV7ymTv/UM1EGGm2OuuN7MhbXHB4HPYQLaEsQOa@postgresql.org X-Gm-Message-State: AOJu0Yx7U7yBObLwZyp2eqGo+n3Ig7QXKFDeMDM0n/pOkivxWCl4JFp0 yB7zSXLRrIR7RNhRvnJPIeBvZQuvdiC37E2H3ExQaWjh2qFe0ShydGO1sWmpj4i92Dm0tooybW7 hAPZkxd4KgdlwGJ5SzRpw45Xz5sQ= X-Gm-Gg: ASbGncvVaxgInJW367D/KwmHWk1WNdvoICo3f/sNPchC7MEJVvF5n8AgFeeWijRnveD iLHwreSSX6P32/Vz8u4vns/g6VMHKxG4OD9RIjhYNfRyjjikdsSsWnDZsX62rwA5QoWk0he8UUY lM9UVAJTpdMgHaF5qRN3Qsx4mS X-Google-Smtp-Source: AGHT+IFOQ9E7/15F1I3UT+d85D0NmDcZSnqgUleOaaMIcHE7NuOzB5RJLtQNSGlAVnmqsQLzNnDviT4wO9s3KMkJiTA= X-Received: by 2002:a05:6870:4688:b0:29e:7d35:2319 with SMTP id 586e51a60fabf-2c78027642bmr2399282fac.4.1742572533585; Fri, 21 Mar 2025 08:55:33 -0700 (PDT) MIME-Version: 1.0 References: <6f2f2167f4be09e6ca9251c8f69dfe01809d68be.camel@cybertec.at> <88e3b55a-8ef8-4b53-8d71-6bfde1a07bc1@oss.nttdata.com> In-Reply-To: From: "David G. Johnston" Date: Fri, 21 Mar 2025 08:54:55 -0700 X-Gm-Features: AQ5f1Jpg9Vlek8iQ7UzTgB1ORuH1bz4Gxq2ExvBo8K8cWbFMwPrFXwXom4iuvB0 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="000000000000dc21f90630dc4827" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000dc21f90630dc4827 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 20, 2025 at 11:13=E2=80=AFAM Nathan Bossart wrote: > > How does something like this look for the comment? > > /* > * isset_offset is an optional offset of a field in the result > struct > * that stores whether the value is explicitly set for the > relation or > * has just picked up the default value. In most cases, this can > be > * deduced by giving the reloption a special default value (e.g., > -2 is > * a common one for integer reloptions), but this isn't always > * possible. One notable example is Boolean reloptions, where it= 's > * difficult to discern the source of the value. This offset is > only > * used if given a value greater than zero. > */ > int isset_offset; > > > I didn't actually come back to this before writing my comment. I'm glad they both say basically the same thing. I'm still partial to mine but yours probably fits the overall style of the codebase better. David J. --000000000000dc21f90630dc4827 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Mar 20, 2025 at 11:13=E2=80=AFAM Nathan Bossart &l= t;nathandbossart@gmail.com&= gt; wrote:

How does something like this look for the comment?

=C2=A0 =C2=A0 =C2=A0 =C2=A0 /*
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* isset_offset is an optional offset of a= field in the result struct
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* that stores whether the value is explic= itly set for the relation or
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* has just picked up the default value.= =C2=A0 In most cases, this can be
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* deduced by giving the reloption a speci= al default value (e.g., -2 is
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* a common one for integer reloptions), b= ut this isn't always
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* possible.=C2=A0 One notable example is = Boolean reloptions, where it's
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* difficult to discern the source of the = value.=C2=A0 This offset is only
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* used if given a value greater than zero= .
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*/
=C2=A0 =C2=A0 =C2=A0 =C2=A0 int=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0isset_offset;



I didn't actually come back=C2= =A0to this before writing my comment.

I'm glad the= y both say basically the same thing.

I'm still par= tial to mine but yours probably fits the overall style of the codebase bett= er.

David J.

--000000000000dc21f90630dc4827--