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 1sT0aG-00CCFl-RH for pgsql-hackers@arkaria.postgresql.org; Sun, 14 Jul 2024 14:52:16 +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 1sT0aF-005re6-9S for pgsql-hackers@arkaria.postgresql.org; Sun, 14 Jul 2024 14:52:15 +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 1sT0aE-005rdy-W6 for pgsql-hackers@lists.postgresql.org; Sun, 14 Jul 2024 14:52:14 +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 1sT0aC-0021Ws-Dq for pgsql-hackers@lists.postgresql.org; Sun, 14 Jul 2024 14:52:13 +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 46EEpsOd2779386; Sun, 14 Jul 2024 10:51:54 -0400 From: Tom Lane To: Peter Eisentraut cc: Thomas Munro , Heikki Linnakangas , Japin Li , Andres Freund , PostgreSQL Hackers Subject: Re: Cannot find a working 64-bit integer type on Illumos In-reply-to: References: <20240322165305.6zrtxcmzdrywvmsu@awork3.anarazel.de> <944094.1711128356@sss.pgh.pa.us> <1229869.1711160593@sss.pgh.pa.us> <7cf1dcb7-306f-4418-bf25-bdc75130db10@eisentraut.org> Comments: In-reply-to Peter Eisentraut message dated "Sun, 14 Jul 2024 15:47:50 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2779384.1720968714.1@sss.pgh.pa.us> Date: Sun, 14 Jul 2024 10:51:54 -0400 Message-ID: <2779385.1720968714@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut writes: > On 04.07.24 03:55, Thomas Munro wrote: >>> Personally, I find "PRId64" pretty unreadable. "INT64_MODIFIER" wasn't >>> nice either, though, and following standards is good, so I'm sure I'll >>> get used to it. > Using PRId64 would be very beneficial because gettext understands it, > and so we would no longer need the various workarounds for not putting > INT64_FORMAT into the middle of a translated string. Uh, really? The translated strings live in /usr/share, which is expected to be architecture-independent, so how would they make that work? regards, tom lane