pgsql: Reduce log verbosity of startup/shutdown for launcher subprocess

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Reduce log verbosity of startup/shutdown for launcher subprocess
Date: 2017-03-10 20:18:44
Message-ID: E1cmQzs-0003pz-PQ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Reduce log verbosity of startup/shutdown for launcher subprocesses.

There's no really good reason why the autovacuum launcher and logical
replication launcher should announce themselves at startup and shutdown
by default. Users don't care that those processes exist, and it's
inconsistent that those background processes announce themselves while
others don't. So, reduce those messages from LOG to DEBUG1 level.

I was sorely tempted to reduce the "starting logical replication worker
for subscription ..." message to DEBUG1 as well, but forebore for now.
Those processes might possibly be of direct interest to users, at least
until logical replication is a lot better shaken out than it is today.

Discussion: https://postgr.es/m/19479.1489121003@sss.pgh.pa.us

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/6ec4c8584c45ee784a95e02c40bb643430dee32a

Modified Files
--------------
src/backend/postmaster/autovacuum.c | 4 ++--
src/backend/replication/logical/launcher.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-03-10 20:32:50 pgsql: pg_dump: Fix dumping of publications
Previous Message Robert Haas 2017-03-10 19:53:32 pgsql: Revert "Use group updates when setting transaction status in clo