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 1lx3Y3-0003Ax-Qa for pgsql-hackers@arkaria.postgresql.org; Sat, 26 Jun 2021 08:20:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lx3Y2-0007hA-QN for pgsql-hackers@arkaria.postgresql.org; Sat, 26 Jun 2021 08:20: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 1lx3Y2-0007h1-IS for pgsql-hackers@lists.postgresql.org; Sat, 26 Jun 2021 08:20:18 +0000 Received: from sfr-1.cri.mines-paristech.fr ([77.158.180.225] helo=smtp.cri.ensmp.fr) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lx3Xw-0003jx-UF for pgsql-hackers@postgresql.org; Sat, 26 Jun 2021 08:20:18 +0000 Received: from pseudo (185.141.6.84.rev.sfr.net [84.6.141.185]) by smtp.cri.ensmp.fr (Postfix) with ESMTPSA id DBC60C05B7; Sat, 26 Jun 2021 10:22:08 +0200 (CEST) Date: Sat, 26 Jun 2021 10:20:11 +0200 (CEST) From: Fabien COELHO X-X-Sender: fabien@pseudo To: Yugo NAGATA cc: Thomas Munro , Marina Polyakova , Alvaro Herrera , pgsql-hackers , Teodor Sigaev Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors In-Reply-To: <20210625200113.b411821946a08b5f7d6b8f73@sraoss.co.jp> Message-ID: References: <20181116195952.nq4ak4r7cbzvoher@alvherre.pgsql> <20210524112910.444fbfdfbff747bd3b9720ee@sraoss.co.jp> <20210622235459.4b2e38e268488014226b3262@sraoss.co.jp> <20210625200113.b411821946a08b5f7d6b8f73@sraoss.co.jp> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="2056645051-674257208-1624695611=:482873" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2056645051-674257208-1624695611=:482873 Content-Type: text/plain; charset=ISO-2022-JP; format=flowed Hello Yugo-san, >> I'm wondering whether we could use "vars" instead of "variables" as a >> struct field name and function parameter name, so that is is shorter and >> more distinct from the type name "Variables". What do you think? > > The struct "Variables" has a field named "vars" which is an array of > "Variable" type. I guess this is a reason why "variables" is used instead > of "vars" as a name of "Variables" type variable so that we could know > a variable's type is Variable or Variables. Also, in order to refer to > the field, we would use > > vars->vars[vars->nvars] > > and there are nested "vars". Could this make a codereader confused? Hmmm… Probably. Let's keep "variables" then. -- Fabien. --2056645051-674257208-1624695611=:482873--