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 1q04v8-0004Wb-LF for pgsql-hackers@arkaria.postgresql.org; Fri, 19 May 2023 18:33:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q04v7-0002aB-7r for pgsql-hackers@arkaria.postgresql.org; Fri, 19 May 2023 18:33:41 +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 1q04v6-0002a2-Ut for pgsql-hackers@lists.postgresql.org; Fri, 19 May 2023 18:33:40 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q04v4-000icm-Hr for pgsql-hackers@lists.postgresql.org; Fri, 19 May 2023 18:33:39 +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 34JIXaOI281325; Fri, 19 May 2023 14:33:36 -0400 From: Tom Lane To: Amit Langote cc: Nathan Bossart , Aleksander Alekseev , PostgreSQL Hackers Subject: Re: The documentation for READ COMMITTED may be incomplete or wrong In-reply-to: References: <3794290.1684421615@sss.pgh.pa.us> <3798164.1684423374@sss.pgh.pa.us> <20230518195123.GA3362715@nathanxps13> <3880859.1684440216@sss.pgh.pa.us> <20230518213442.GA3364784@nathanxps13> <4024583.1684448782@sss.pgh.pa.us> <4111741.1684454234@sss.pgh.pa.us> Comments: In-reply-to Amit Langote message dated "Fri, 19 May 2023 21:53:45 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <281323.1684521216.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 19 May 2023 14:33:36 -0400 Message-ID: <281324.1684521216@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Amit Langote writes: > On Fri, May 19, 2023 at 8:57 AM Tom Lane wrote: >> What I'm thinking about doing to back-patch this is to replace >> one of the pointer fields in EPQState with a pointer to a >> subsidiary palloc'd structure, where we can put the new fields >> along with the cannibalized old one. We've done something >> similar before, and it seems a lot safer than having basically >> different logic in v16 than earlier branches. > +1. Done that way. I chose to replace the tuple_table field, because it was in a convenient spot and it seemed like the field least likely to have any outside code referencing it. regards, tom lane