Re: Unified logging system for command-line programs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Unified logging system for command-line programs
Date
Msg-id 4159.1546553023@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unified logging system for command-line programs  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Unified logging system for command-line programs  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 03/01/2019 22:01, Tom Lane wrote:
>> 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.

Right, so for that you'd use ereport(WARNING) or LOG or whatever.

We'd probably need a bit of care about which ereport levels produce
exactly what output, but I don't think that's insurmountable.  We
do not need all the backend-side message levels to exist for frontend.

            regards, tom lane


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Delay locking partitions during query execution
Next
From: Andres Freund
Date:
Subject: Re: Unified logging system for command-line programs