Re: pgsql: Remove function names from error messages

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Remove function names from error messages
Date: 2018-12-21 14:05:37
Message-ID: 20181221140537.3qxe4atr6xg6lwzc@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 2018-Dec-20, Michael Paquier wrote:

> On Wed, Dec 19, 2018 at 05:53:48PM +0000, Alvaro Herrera wrote:
> > Remove function names from error messages
> >
> > They are not necessary, and having them there gives useless work for
> > translators.
>
> I am spotting a couple of extra ones for functions:
> src/backend/access/transam/xlog.c:
> (errmsg("pg_stop_backup cleanup done, waiting for required WAL segments
> to be archived")));

Yeah, I grepped for other uses and found format() being mentioned too,
but there didn't seem to be any repetition in the messages other than
the ones I patched, so I didn't bother. Thanks for following through
with these ones in the other thread.

I grepped using '()' as part of the pattern to find function names;
maybe there's a more comprehensive way.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2018-12-21 15:49:14 Re: pgsql: Check for conflicting queries during replay of gistvacuumpage()
Previous Message Alexander Korotkov 2018-12-20 23:38:20 pgsql: Check for conflicting queries during replay of gistvacuumpage()