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 1phhcL-0006tV-4i for pgsql-bugs@arkaria.postgresql.org; Thu, 30 Mar 2023 02:02:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1phhcI-00049m-Sv for pgsql-bugs@arkaria.postgresql.org; Thu, 30 Mar 2023 02:02:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1phhcI-00045U-Ji for pgsql-bugs@lists.postgresql.org; Thu, 30 Mar 2023 02:02:18 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1phhcF-00032F-Pq for pgsql-bugs@postgresql.org; Thu, 30 Mar 2023 02:02:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 32U229kH4119645; Wed, 29 Mar 2023 22:02:09 -0400 From: Tom Lane To: David Rowley cc: Andres Freund , Richard Guo , =?UTF-8?B?55SE5piO5rSL?= , pgsql-bugs@postgresql.org Subject: Re: A structure has changed but comment modifications maybe missed In-reply-to: References: <1a96696c.9d3.187193989c3.Coremail.zhenmingyang@yeah.net> Comments: In-reply-to David Rowley message dated "Thu, 30 Mar 2023 14:55:53 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4119643.1680141729.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 29 Mar 2023 22:02:09 -0400 Message-ID: <4119644.1680141729@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Rowley writes: > I think the attached is what you have in mind. Can you confirm? tts_nvalid is still a thing, so I question your edit here: --- a/src/include/executor/tuptable.h +++ b/src/include/executor/tuptable.h @@ -68,8 +68,7 @@ * A TupleTableSlot can also be "empty", indicated by flag TTS_FLAG_EMPTY= set * in tts_flags, holding no valid data. This is the only valid state for= a * freshly-created slot that has not yet had a tuple descriptor assigned = to - * it. In this state, TTS_SHOULDFREE should not be set in tts_flags, tts= _tuple - * must be NULL and tts_nvalid zero. + * it. In this state, TTS_FLAG_SHOULDFREE should not be set in tts_flags= . * * The tupleDescriptor is simply referenced, not copied, by the TupleTabl= eSlot * code. The caller of ExecSetSlotDescriptor() is responsible for provid= ing Andres would really be the expert about these changes though. regards, tom lane