On Wed, Apr 15, 2015 at 4:55 PM, Heikki Linnakangas wrote: > On 04/15/2015 06:41 AM, Fujii Masao wrote: >> Another question is; should we output the progress report to stderr rather >> than stdout? I thought this because I found that pg_basebackup reports >> the progress to stderr. > > > Yeah, probably. We should go through all the output and figure out where > each kind of message needs to do. Should follow the principle Alvaro laid > out > (http://www.postgresql.org/message-id/20150407205320.gn4...@alvh.no-ip.org), > and also make sure it's consistent with pg_basebackup and other tools. > Michael's patch changed some of the logging but we should take a more > holistic look at the situation. And add a comment somewhere explaining the > principle.
Isn't what we are looking for here a common set of frontend-only APIs, let's say as src/common/logging.c? All the tools we have could use it without knowing if they output on stdout and stderr. -- Michael -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
