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.94.2) (envelope-from ) id 1so8r8-008brG-5S for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Sep 2024 21:57:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1so8r7-0032R2-Sd for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Sep 2024 21:57:01 +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.94.2) (envelope-from ) id 1so8r7-0032Qi-IW for pgsql-hackers@lists.postgresql.org; Tue, 10 Sep 2024 21:57:01 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1so8r4-000WsN-Ip for pgsql-hackers@lists.postgresql.org; Tue, 10 Sep 2024 21:57:00 +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 48ALulpM3706657; Tue, 10 Sep 2024 17:56:47 -0400 From: Tom Lane To: Masahiko Sawada cc: Noah Misch , Joe Conway , Peter Eisentraut , Alexander Korotkov , "Guo, Adam" , "pgsql-hackers@lists.postgresql.org" , Nathan Bossart , Jim Mlodgenski Subject: Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation In-reply-to: References: <1696557.1714498172@sss.pgh.pa.us> <2652929.1714745623@sss.pgh.pa.us> <3846ef0f-5273-41aa-a77e-f92841e0515f@eisentraut.org> <362570f3-1031-4f8e-a077-81c103200b64@joeconway.com> <20240518214546.e8@rfd.leadboat.com> <20240831031038.31.nmisch@google.com> <20240906215937.f7.nmisch@google.com> <2385726.1725662213@sss.pgh.pa.us> <3317883.1725925337@sss.pgh.pa.us> <3364732.1725949535@sss.pgh.pa.us> <3542370.1725994675@sss.pgh.pa.us> Comments: In-reply-to Masahiko Sawada message dated "Tue, 10 Sep 2024 14:51:51 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3706655.1726005407.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Tue, 10 Sep 2024 17:56:47 -0400 Message-ID: <3706656.1726005407@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Masahiko Sawada writes: > On Tue, Sep 10, 2024 at 11:57 AM Tom Lane wrote: >> Yeah, that seems like it could work. But are we sure that replicas >> get a copy of the primary's control file rather than creating their >> own? > Yes, I think so. Since at least the system identifiers of primary and > replicas must be identical for physical replication, if replicas use > their own control files then they cannot start the replication. Got it. So now I'm wondering if we need all the complexity of storing stuff in the GIN metapages. Could we simply read the (primary's) signedness out of pg_control and use that? We might need some caching mechanism to make that cheap enough, but accessing the current index's metapage is far from free either. regards, tom lane