Re: libpq error message refactoring - Mailing list pgsql-hackers

From Andres Freund
Subject Re: libpq error message refactoring
Date
Msg-id 20220922154225.q4rtgzzsq6pd4f5x@awork3.anarazel.de
Whole thread Raw
In response to libpq error message refactoring  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: libpq error message refactoring
List pgsql-hackers
Hi,

On 2022-08-25 16:34:26 +0200, Peter Eisentraut wrote:
> libpq now contains a mix of error message strings that end with newlines and
> don't end with newlines, due to some newer code paths with new ways of
> passing errors around.  This has now gotten me confused a few too many times
> both during development and translation.  So I looked into whether we can
> unify this, similar to how we have done elsewhere (e.g., pg_upgrade).  I
> came up with the attached patch.  It's not complete, but it shows the idea
> and it looks like a nice simplification to me. Thoughts on this approach?

This patch has been failing for a while:
https://cirrus-ci.com/github/postgresql-cfbot/postgresql/commitfest/39/3854

Interestingly, previously the error only happened when targetting windows, but
meson also shows it on freebsd.

It's not the cause of this failure, I think, but doesn't appendPQExpBufferVA
need to be added to exports.txt?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: John Morris
Date:
Subject: Re: Temporary file access API
Next
From: Andres Freund
Date:
Subject: Re: Summary function for pg_buffercache