From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
cc: Andres Freund <andres@anarazel.de>,
        pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Unified logging system for command-line programs
In-reply-to: <d6e0e58c-e103-c287-b410-2c872067e020@2ndquadrant.com>
References: <6a609b43-4f57-7348-6480-bd022f924310@2ndquadrant.com>
 <21141.1546199123@sss.pgh.pa.us>
 <20181231155557.7mokxwg7fnvoxd4a@alap3.anarazel.de>
 <841dd9fb-3550-dce0-e9ff-8f64cac9f15d@2ndquadrant.com>
 <20190103180315.o4gh3id5quh5aebc@alap3.anarazel.de>
 <a7c07b9c-8aa4-f9bb-e9eb-30111b732645@2ndquadrant.com>
 <6174.1546549274@sss.pgh.pa.us>
 <d6e0e58c-e103-c287-b410-2c872067e020@2ndquadrant.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
	message dated "Thu, 03 Jan 2019 22:38:17 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4158.1546553023.1@sss.pgh.pa.us>
Date: Thu, 03 Jan 2019 17:03:43 -0500
Message-ID: <4159.1546553023@sss.pgh.pa.us>
Precedence: bulk

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