On 03/01/2019 22:01, Tom Lane wrote:
> I envisioned that we'd have a wrapper in which
> non-error ereports() map directly onto what you're calling
> pg_log_debug, pg_log_warning, etc,
My code does that, but the other way around. (It's easier that way than
to unpack ereport() invocations.)
> while ereport(ERROR) has the
> effect of writing a message and then calling exit(1).
The problem is that in majority of cases the FRONTEND code, as it is
written today, doesn't want to exit() after an error.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services