Re: Add Information during standby recovery conflicts - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Add Information during standby recovery conflicts
Date
Msg-id 20201013224408.GA5517@alvherre.pgsql
Whole thread Raw
In response to Re: Add Information during standby recovery conflicts  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Responses Re: Add Information during standby recovery conflicts
List pgsql-hackers
On 2020-Oct-14, Masahiko Sawada wrote:

> I've attached the patch as an idea of fixing the above comments as
> well as the comment from Alvaro. I can be applied on top of v4 patch.

One note about the translation stuff.  Currently you have _("...") where
the string is produced, and then ereport(.., errmsg("%s", str) where it
is used.  Both those things will attempt to translate the string, which
isn't great.  It is better if we only translate once.  You have two
options to fix this: one is to change _() to gettext_noop() (which marks
the string for translation so that it appears in the message catalog,
but it does not return the translation -- it returns the original, and
then errmsg() translates at run time).  The other is to change errmsg()
to errmsg_internal() .. so the function returns the translated message
and errmsg_internal() doesn't apply a translation.

I prefer the first option, because if we ever include a server feature
to log both the non-translated message alongside the translated one, we
will already have both in hand.



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Add Information during standby recovery conflicts
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: archive status ".ready" files may be created too early