Re: Unified logging system for command-line programs
Tom Lane <tgl@sss.pgh.pa.us>
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>
Date: 2019-01-03T22:03:43Z
Lists: 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
Commits
-
Unified logging system for command-line programs
- cc8d41511721 12.0 landed
-
Assorted translatable string fixes
- 55a70a023c3d 10.0 cited