Re: Emit extra debug message when executing extension script.
От | Robert Haas |
---|---|
Тема | Re: Emit extra debug message when executing extension script. |
Дата | |
Msg-id | CA+TgmoZDeNN4F89R1RFZU0eaROL4yGYTpdJ3B+cdirYoYmKc2A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Emit extra debug message when executing extension script. (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: Emit extra debug message when executing extension script.
|
Список | pgsql-hackers |
On Mon, Jul 4, 2022 at 5:27 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > 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. Yeah, I'm aware of that in general, but I'm not quite clear on how we decide that. Do we take the view that all debug-level messages need not be translated? -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: