pgsql: postmaster: Start syslogger earlier

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: postmaster: Start syslogger earlier
Date: 2019-01-30 20:14:31
Message-ID: E1gowFj-0000nz-5B@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

postmaster: Start syslogger earlier

When the syslogger was originally
added (bdf8ef6925de6ea1a9330fa1ce32e1a315d07eb2), nothing was normally
logged before the point where it was started. But since
f9dfa5c9776649f769d537dd0923003b35f128de, the creation of sockets
causes messages of level LOG to be written routinely, so those don't
go to the syslogger now.

To improve that, arrange the sequence in PostmasterMain() slightly so
that the syslogger is started early enough to capture those messages.

Discussion: https://www.postgresql.org/message-id/d5d50936-20b9-85f1-06bc-94a01c5040c1%402ndquadrant.com
Reviewed-by: Christoph Berg <christoph(dot)berg(at)credativ(dot)de>

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/57431a911d3a650451d198846ad3194900666152

Modified Files
--------------
src/backend/postmaster/postmaster.c | 120 ++++++++++++++++++------------------
1 file changed, 60 insertions(+), 60 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2019-01-30 22:29:04 pgsql: Log PostgreSQL version number on startup
Previous Message Tom Lane 2019-01-30 17:59:21 Re: pgsql: Change error handling of out of scope variables in ecpg.