Increase footprint of %m and reduce strerror()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Increase footprint of %m and reduce strerror()
Date: 2019-11-29 06:51:15
Message-ID: 20191129065115.GM2505@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi all,

Since commit d6c55de1, we support %m in the in-core port for printf
and such. And it seems to me that we could do better for the frontend
code by reducing the dependency to strerror().

One advantage of doing a switch, or at least reduce the use of
strerror(), would be to ease the work of translators with more error
messages unified between the frontend and the backend. A possible
drawback is that this could be a cause of minor conflicts when
back-patching. Always easy enough to fix, still that can be
annoying.

Thoughts?
--
Michael

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Takuma Hoshiai 2019-11-29 07:10:40 Re: Implementing Incremental View Maintenance
Previous Message Yugo Nagata 2019-11-29 06:50:06 Re: To Suggest a "DROP INCREMENTAL MATERIALIZED VIEW" in psql, but the syntax error when you run.