pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: libpq error message refactoring
Date: Thu, 22 Sep 2022 22:48:01 -0400
Message-ID: <2033449.1663901281@sss.pgh.pa.us> (raw)
In-Reply-To: <20220923024543.fki3zdhyscxof6f7@awork3.anarazel.de>
References: <7c0232ef-7b44-68db-599d-b327d0640a77@enterprisedb.com>
	<20220922154225.q4rtgzzsq6pd4f5x@awork3.anarazel.de>
	<d5dddca7-9bdc-ee18-1ec9-ee21f8302d4a@enterprisedb.com>
	<20220923022727.mclhsv3cjbmdrrkd@awork3.anarazel.de>
	<20220923024543.fki3zdhyscxof6f7@awork3.anarazel.de>

Andres Freund <andres@anarazel.de> 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

view thread (14+ messages)  latest in thread

Message-ID: <2033449.1663901281@sss.pgh.pa.us>
Permalink:  ../2033449.1663901281@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2033449.1663901281@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, peter.eisentraut@enterprisedb.com
  Subject: Re: libpq error message refactoring
  In-Reply-To: <2033449.1663901281@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox