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

From Andres Freund
Subject Re: Unified logging system for command-line programs
Date
Msg-id 20181231155557.7mokxwg7fnvoxd4a@alap3.anarazel.de
Whole thread Raw
In response to Re: Unified logging system for command-line programs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unified logging system for command-line programs  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Hi,

On 2018-12-30 14:45:23 -0500, Tom Lane wrote:
> I wonder how hard it would be to layer some subset of
> ereport() functionality on top of what you have here, so as to get
> rid of those #ifdef stanzas.

+many.  I think we should aim to unify the use (in contrast to the
implementation) of logging as much as possible, rather than having a
separate API for it for client programs. Not just because that facilitates
code reuse in frontend programs, but also because that's one less thing to
learn when getting started with PG.

Further down the line I think we should also port the PG_CATCH logic to
client programs.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Erik Rijkers
Date:
Subject: Re: [HACKERS] proposal: schema variables
Next
From: Nikolay Shaplov
Date:
Subject: [PATCH] check for ctags utility in make_ctags