| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Frontend error logging style |
| Date: | 2021-11-19 15:18:55 |
| Message-ID: | CA+TgmoYaA1wtU91yNg1_C6oS8azAfp5dQ1YrfuNAm2=Yefrn1A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 19, 2021 at 5:17 AM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2021-11-19 15:19:02 | Re: wait event and archive_command |
| Previous Message | Fujii Masao | 2021-11-19 15:18:15 | Re: issue in pgfdw_report_error()? |