Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pgcFQ-0004Tx-Hg for pgsql-bugs@arkaria.postgresql.org; Mon, 27 Mar 2023 02:06:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pgcFO-0008GO-Gn for pgsql-bugs@arkaria.postgresql.org; Mon, 27 Mar 2023 02:06:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pgcFO-0008GD-64 for pgsql-bugs@lists.postgresql.org; Mon, 27 Mar 2023 02:06:10 +0000 Received: from mail-yb1-xb2a.google.com ([2607:f8b0:4864:20::b2a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pgcFL-0001AO-Lk for pgsql-bugs@postgresql.org; Mon, 27 Mar 2023 02:06:09 +0000 Received: by mail-yb1-xb2a.google.com with SMTP id r187so8622435ybr.6 for ; Sun, 26 Mar 2023 19:06:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679882767; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=EN2zdjLHQywhWQJs6BWrNDfD13z+5OEUEAq3pvnxf4s=; b=OZUyzM0e01itqc9gcJE3C6teD812rYtt19BdV/ZKPtA89Y9Za04BHQ0wRcs0+Di39g oqOdU8UWflPMHKMFOhC7/hHhjoqNewcIPqM2g2eF3V4ZVzYvwGMJI7oy0e5sktETL6Wg /ug1QQFfzJdEMh5K453wttI+PG9Lh0cIx0LJDIcPhAHtRLsrLMVD+LELMyUWbku9IXsF cAQGPZeMuT28xVbHU6rBkVH/nd3wzEtFAUfesRSaWlM4m9keDn3TJ69tW4yX5jdQgqCD k64fNFFFv6f5JfkpCgZlEOE7R6Pwvm60h2pj+5m863s60mFwha8mhNPkRwnBW7RJmqbj tUSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679882767; 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=EN2zdjLHQywhWQJs6BWrNDfD13z+5OEUEAq3pvnxf4s=; b=XTdkBRcB3yH0ZuAGiRGy1qE4an2a/IaE8OJEr6tJUw8djyYM9tmSi7TqpdxsgIFPUr RASQAh49esMGNCNrmDD9y1rR2nItJnGxpV17fozRHHJzSD0nxWdvZ5BE7093XpWDNCgR JzAwKsiKK8mlhWmHUg7NkluzJXAmE3Qh+mWJmUmDF9QTNTtDaZ16yGp4fT1vT5ztY5rW 8LtDxNYbiuC2KY8rXgjvfUW9pRyQon02LApeHpqEO9vdl5i0+YcyxbSG+ASE2Pe+cDML Xncsz+Y1LYyw/9hX/bhIs6PwEbqf3Obu0uF8OQcPadAPTP+z5g6que5LcPJwf5sKIbc4 CW4A== X-Gm-Message-State: AAQBX9f3s1sSXeuJf1GkbtSVsXDkcdDD0h0VTvOY1CuzHA13xRsF80Vv vjdy41i7V38qCV+vSbZqx7OhvRx/amOKMteoritAkJ6gs6c= X-Google-Smtp-Source: AKy350a994GjXoY45b8x5qblu9ryFOKvz6e4FSPcFsCrsbot1AhEtW8ygsSuKFsmvoVe069W4eDwcGr7VSREnJ/V6IA= X-Received: by 2002:a05:6902:72e:b0:b6c:f26c:e5ab with SMTP id l14-20020a056902072e00b00b6cf26ce5abmr6482298ybt.3.1679882766808; Sun, 26 Mar 2023 19:06:06 -0700 (PDT) MIME-Version: 1.0 References: <1a96696c.9d3.187193989c3.Coremail.zhenmingyang@yeah.net> In-Reply-To: <1a96696c.9d3.187193989c3.Coremail.zhenmingyang@yeah.net> From: Richard Guo Date: Mon, 27 Mar 2023 10:05:55 +0800 Message-ID: Subject: Re: A structure has changed but comment modifications maybe missed To: =?UTF-8?B?55SE5piO5rSL?= Cc: pgsql-bugs@postgresql.org Content-Type: multipart/alternative; boundary="000000000000947a1605f7d82f15" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000947a1605f7d82f15 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Mar 25, 2023 at 10:43=E2=80=AFPM =E7=94=84=E6=98=8E=E6=B4=8B wrote: > Recently when I was reading the TupleTableSlot code, I noticed that the > field "tts_tuple" mentioned in the comment has been removed in the higher > version, but it still exists in the comment. > location=EF=BC=9A > > https://github.com/postgres/postgres/blob/master/src/include/executor/tup= table.h > src/include/executor/tuptable.h=EF=BC=9A71 > src/include/executor/tuptable.h=EF=BC=9A271 > Good catch. This should be a minor oversight in 4da597ed, in which the TupleTableSlot implementation has been splitted into different slot types, and tts_tuple has been removed from TupleTableSlot struct. Besides, at tuptable.h:71, I think TTS_SHOULDFREE should be TTS_FLAG_SHOULDFREE. Thanks Richard --000000000000947a1605f7d82f15 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Sat, Mar 25, 2023 at 10:43=E2=80=AFPM = =E7=94=84=E6=98=8E=E6=B4=8B <zh= enmingyang@yeah.net> wrote:
Recently when I was read= ing the TupleTableSlot code, I noticed that the field "tts_tuple"= mentioned in the comment has been removed in the higher version, but it st= ill exists in the comment.
location=EF=BC=9A=
--000000000000947a1605f7d82f15--