Re: libpq error message refactoring

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq error message refactoring
Date: 2022-09-23 20:31:03
Message-ID: 20eff6cb-4471-ebcb-465c-ed9052d7fc63@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23.09.22 04:45, Andres Freund wrote:
> On 2022-09-22 19:27:27 -0700, Andres Freund wrote:
>> I just noticed it when trying to understand the linker failure - which I
>> still don't...
>
> Heh, figured it out. It's inside #ifdef ENABLE_NLS. So it fails on all
> platforms without NLS enabled.

Hah!

Here is an updated patch to get the CI clean. I'll look into the other
discussed issues later.

Attachment Content-Type Size
v2-0001-WIP-libpq_append_error.patch text/plain 40.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-09-23 20:45:09 Re: pg_stat_have_stats() returns true for dropped indexes (or for index creation transaction rolled back)
Previous Message Nathan Bossart 2022-09-23 20:24:39 Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes?