Re: [PATCH] libpq: Wrap out-of-memory error messages with libpq_gettext()

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Joshua Shanks <jjshanks(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] libpq: Wrap out-of-memory error messages with libpq_gettext()
Date: 2025-11-10 07:04:04
Message-ID: CAHGQGwFjWV6qAr1sr43PQkXdqBL3N+h3ybvuwaJ=oV=6=ku4+w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 9, 2025 at 5:21 AM Joshua Shanks <jjshanks(at)gmail(dot)com> wrote:
>
> Hi,
>
> The recent patch for passwordFromFile() error handling highlighted that many other out-of-memory error messages in libpq still aren't wrapped with libpq_gettext().
>
> Attached is a patch that systematically wraps the remaining bare "out of memory" strings across libpq with libpq_gettext() to ensure consistent translation support. This covers:
> - Authentication modules (fe-auth.c, fe-auth-scram.c, fe-auth-oauth.c)
> - Connection handling (fe-connect.c, fe-cancel.c)
> - Protocol and secure communication (fe-protocol3.c, fe-secure-*.c)
> - Other modules (fe-exec.c, fe-lobj.c, fe-gssapi-common.c)

- libpq_append_conn_error(conn, "out of memory");
+ libpq_append_conn_error(conn, libpq_gettext("out of memory"));

Seems libpq_gettext() doesn't need to be called here,
since libpq_append_conn_error() already does that internally. No?

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-11-10 07:30:38 Re: display hot standby state in psql prompt
Previous Message Pavel Stehule 2025-11-10 06:40:30 Re: proposal: schema variables