Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vs7tW-0070KU-0i for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Feb 2026 23:20:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vs7tV-006Ne2-07 for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Feb 2026 23:20:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vs7tU-006Nds-1T for pgsql-hackers@lists.postgresql.org; Mon, 16 Feb 2026 23:20:44 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vs7tQ-00000000xzc-3dIw for pgsql-hackers@postgresql.org; Mon, 16 Feb 2026 23:20:43 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=SSZpQdAEoDYv00kTGWZAdvBlJrKPZjf24+RBH9Eqii4=; b=qgG4IGW8gDVv9UUkA3kGTIkPa5 wEyGzXnoqmwbunvGRlZF3DrXPy9UJGRY8d/ZTh9Aa7AEOno0U0deP2OaMCA618aLjV+Yf1OdpXTKb kLrUoB7SBPhWPVVebmLCYlfFkdX8Oo0NDN0rxohEdKPwrIqvR6e8TO2zvKH29hsyJ0zR1rY3Oyxl2 RGN9Z6JB6hOt6Jng/EzNC6kBnStBC1Le6yHIdn3DNKuNBB5vgshcLk7RTdBurEdYqtxbkJnPnNK/e I154RVO9xFA2MHDfJwcO7yEaD5SDYJRuAslV9oDrX8y0qegtVtwysXYt4zsZBpbf9KhA1sfmNtZ61 CI6tjPqg==; Received: from [2409:11:4120:300:6bb6:558:dab6:f739] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vs7tJ-0036zB-1p; Mon, 16 Feb 2026 23:20:35 +0000 Date: Tue, 17 Feb 2026 08:20:20 +0900 (JST) Message-Id: <20260217.082020.1713532024309739607.ishii@postgresql.org> To: assam258@gmail.com Cc: vik@postgresfriends.org, er@xs4all.nl, jacob.champion@enterprisedb.com, david.g.johnston@gmail.com, peter@eisentraut.org, pgsql-hackers@postgresql.org Subject: Re: Row pattern recognition From: Tatsuo Ishii In-Reply-To: References: <20260215.180652.676783304925959084.ishii@postgresql.org> X-Mailer: Mew version 6.8 on Emacs 29.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:6bb6:558:dab6:f739 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Henson, > Hi Tatsuo, > > Thanks for rebasing to v43! > > I noticed the Cirrus CI 32-bit build (test_world_32) failed on three > tests, all due to the same root cause in rpr_explain.out: > > Sort Method: quicksort Memory: 27kB (expected, 64-bit) > Sort Method: quicksort Memory: 22kB (actual, 32-bit) I noticed that too. > The rpr_explain_filter() function was already normalizing the RPR > Storage memory values, but missed the Sort node's "Memory: NNkB" > which also varies between 32-bit and 64-bit due to pointer/struct > size differences. > > The attached incremental patch adds Sort Method memory normalization > to rpr_explain_filter(), using the same approach as the existing > Storage and Maximum Storage filters. Looks good fix to me. Is that Ok for you to not release v44 patch immediately? Our patch set is very large and I hesitate to post a new patch set too offten. >> The node serialization functions (141 lines, 0% coverage) are the >> > largest untested area. I'm not sure how to trigger these paths >> > in the regression test framework. Any suggestions? >> >> I think we can leave it as it is, until reluctant quantifier is >> implemented. >> > > Agreed. Thanks for agreeing on this. Best regards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp