Re: [PATCH] Log PostgreSQL version number on startup

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Log PostgreSQL version number on startup
Date: 2018-12-10 06:33:07
Message-ID: 20181210063307.GD1105@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 21, 2018 at 11:32:46AM -0500, Stephen Frost wrote:
> * Christoph Berg (christoph(dot)berg(at)credativ(dot)de) wrote:
>> it has bugged me for a long time that there's no clear "PostgreSQL is
>> starting" message in the server log file. I'd like to change that for
>> two reasons:
>
> +1

+1. One complain which could be formulated is that this makes the
logs at startup more noisy. Now your patch has an issue if you want to
ensure that this information gets added to the log files, because at
this stage of startup the GUCs are not loaded, hence this is sent to
stderr, and perhaps not on the log files.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Takahashi, Ryohei 2018-12-10 08:13:21 RE: Too many logs are written on Windows (LOG: could not reserve shared memory region (addr=%p) for child %p:)
Previous Message Michael Paquier 2018-12-10 06:10:36 Re: Use durable_unlink for .ready and .done files for WAL segment removal