Re: Emit extra debug message when executing extension script. - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Emit extra debug message when executing extension script.
Date
Msg-id 20220704092753.ancsnxqg2gltgal4@alvherre.pgsql
Whole thread Raw
In response to Re: Emit extra debug message when executing extension script.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Emit extra debug message when executing extension script.
List pgsql-hackers
On 2022-Jun-29, Robert Haas wrote:

> On Wed, Jun 29, 2022 at 9:26 AM Peter Eisentraut
> <peter.eisentraut@enterprisedb.com> wrote:
> > On 28.06.22 21:10, Jeff Davis wrote:
> > > +     ereport(DEBUG1, errmsg("executing extension script: %s", filename));
> >
> > This should either be elog or use errmsg_internal.
> 
> Why?

The reason is that errmsg() marks the message for translation, and we
don't want to burden translators with messages that are of little
interest to most users.  Using either elog() or errmsg_internal()
avoids that.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"El sudor es la mejor cura para un pensamiento enfermo" (Bardia)



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Using PQexecQuery in pipeline mode produces unexpected Close messages
Next
From: Ken Kato
Date:
Subject: Add last_vacuum_index_scans in pg_stat_all_tables