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 20190401183112.2k5kknfrixip4n3k@alap3.anarazel.de
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
List pgsql-hackers
Hi,

On 2019-02-22 09:39:59 +0100, Peter Eisentraut wrote:
> Here is an updated patch.  I've finished the functionality to the point
> where I'm content with it.  I fixed up some of the remaining special
> cases in pg_dump that I hadn't sorted out last time.  I also moved the
> scattered setvbuf(stderr, ...) handling (for Windows) into a central
> place.  Colors can now be configured, too.
> 
> -- 
> Peter Eisentraut              http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

> From 3e9aadf00ab582fed132e45c5745b1c38a4f59c9 Mon Sep 17 00:00:00 2001
> From: Peter Eisentraut <peter@eisentraut.org>
> Date: Fri, 22 Feb 2019 09:18:55 +0100
> Subject: [PATCH v3] Unified logging system for command-line programs
> 
> This unifies the various ad hoc logging (message printing, error
> printing) systems used throughout the command-line programs.

I'm unhappy about this being committed.  I don't think there was
terribly much buyin for this amount of duplicated infrastructure.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Raymond Martin
Date:
Subject: RE: minimizing pg_stat_statements performance overhead
Next
From: Peter Eisentraut
Date:
Subject: Re: Unified logging system for command-line programs