Re: Frontend error logging style
| От | Robert Haas |
|---|---|
| Тема | Re: Frontend error logging style |
| Дата | |
| Msg-id | CA+TgmoYaA1wtU91yNg1_C6oS8azAfp5dQ1YrfuNAm2=Yefrn1A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Frontend error logging style (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
| Ответы |
Re: Frontend error logging style
|
| Список | pgsql-hackers |
On Fri, Nov 19, 2021 at 5:17 AM Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote: > If people want to do that kind of thing (I'm undecided whether the > complexity is worth it), then make it a different API. The pg_log_* > calls are for writing formatted output. They normalized existing > hand-coded patterns at the time. We can wrap another API on top of them > that does flow control and output. The pg_log_* stuff is more on the > level of syslog(), which also just outputs stuff. Nobody is suggesting > that syslog(LOG_EMERG) should exit the program automatically. But you > can wrap higher-level APIs such as ereport() on top of that that might > do that. Yeah, that might be a way forward. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: