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 1lPGE3-0006zB-MB for pgsql-bugs@arkaria.postgresql.org; Thu, 25 Mar 2021 02:59:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lPGE2-0004CN-LG for pgsql-bugs@arkaria.postgresql.org; Thu, 25 Mar 2021 02:59:58 +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 1lPGE2-0004CG-F2 for pgsql-bugs@lists.postgresql.org; Thu, 25 Mar 2021 02:59:58 +0000 Received: from oss.nttdata.com ([49.212.34.109]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lPGE0-00085I-91 for pgsql-bugs@lists.postgresql.org; Thu, 25 Mar 2021 02:59:58 +0000 Received: from hnk.local (p2350207-ipbf2126funabasi.chiba.ocn.ne.jp [114.167.184.207]) by oss.nttdata.com (Postfix) with ESMTPSA id 27172628CD; Thu, 25 Mar 2021 11:59:50 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.3 at oss.nttdata.com Subject: Re: BUG #16931: source code problem about commit_ts To: Alvaro Herrera Cc: zoulx1982@163.com, pgsql-bugs@lists.postgresql.org References: <20210324163931.GA24841@alvherre.pgsql> From: Fujii Masao Message-ID: <576efafd-30ad-68bb-563c-a5f230cbf588@oss.nttdata.com> Date: Thu, 25 Mar 2021 11:59:49 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210324163931.GA24841@alvherre.pgsql> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021/03/25 1:39, Alvaro Herrera wrote: > On 2021-Mar-24, Fujii Masao wrote: > >> On 2021/03/24 18:05, Alvaro Herrera wrote: >>> Yeah, it seems like a bug. With your patch, the write_xlog=true path >>> becomes unused, and thus the whole COMMIT_TS_SETTS record, so we could >>> remove those things in branch master. The timestamp is acquired from >>> the COMMIT record. >> >> I agree to remove COMMIT_TS_SETTS record from the master branch >> if there are no users or extensions of it. Patch attached. > > Looks good in a quick skim. Let's get this pushed quickly; if anything > exists out there that is calling that code, it'd be good to know sooner > rather than later. However, my feeling is that no such caller exists, > because they would have told us about this problem already. Agreed. I will commit the patch in the master. > Are you bumping WAL page magic? It'd be logical to do so, but on the > other hand if no code exists that is capable of emitting that record, > then it'd be pointless. Yes, I'm thinking to bump WAL page magic because it seems a bit safer. >> Anyway, at first, what about applying the bugfix patch I posted upthread >> to all supported branches? > > Yeah, let's do that. Pushed. Thanks! Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION