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 1obYjY-0003cx-5S for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Sep 2022 02:48:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1obYjX-0000dj-3F for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Sep 2022 02:48:07 +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 1obYjW-0000da-QD for pgsql-hackers@lists.postgresql.org; Fri, 23 Sep 2022 02:48:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1obYjU-0008QA-PM for pgsql-hackers@postgresql.org; Fri, 23 Sep 2022 02:48:06 +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 28N2m1WD2033450; Thu, 22 Sep 2022 22:48:01 -0400 From: Tom Lane To: Andres Freund cc: Peter Eisentraut , pgsql-hackers Subject: Re: libpq error message refactoring In-reply-to: <20220923024543.fki3zdhyscxof6f7@awork3.anarazel.de> References: <7c0232ef-7b44-68db-599d-b327d0640a77@enterprisedb.com> <20220922154225.q4rtgzzsq6pd4f5x@awork3.anarazel.de> <20220923022727.mclhsv3cjbmdrrkd@awork3.anarazel.de> <20220923024543.fki3zdhyscxof6f7@awork3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Thu, 22 Sep 2022 19:45:43 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2033448.1663901281.1@sss.pgh.pa.us> Date: Thu, 22 Sep 2022 22:48:01 -0400 Message-ID: <2033449.1663901281@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > Heh, figured it out. It's inside #ifdef ENABLE_NLS. So it fails on all > platforms without NLS enabled. Argh, how simple! The question about va_start/va_end placement still stands, though. regards, tom lane