Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cmQBM-0000Cn-45 for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2017 19:26:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cmQBL-0001hH-Mz for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2017 19:26:31 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cmQ9p-0003kD-Lo for pgsql-hackers@postgresql.org; Fri, 10 Mar 2017 19:24:57 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cmQ9n-0003OU-KF for pgsql-hackers@postgresql.org; Fri, 10 Mar 2017 19:24:56 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id DF0E720961; Fri, 10 Mar 2017 14:24:54 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Fri, 10 Mar 2017 14:24:54 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=jBgSXs/iYozPNgXeuBj5fhjYMak=; b=tOrRau994+RB55Dlh5cW tRlz3fi+JBIXC81lq9rGQbw26HKHqulR9GWHlomTcJh79MEWiLwO4n3Ww9cnpmeJ V/+8E5bFs1Svs27kyAKFtJdtjlD3RINhSxmPf+tKAb2Ql99aXjix2qSu+xAcLT+2 4ipok0PPTCA0SviiL77Dkos= X-ME-Sender: X-Sasl-enc: lw0FJ4mHZRVyqefbJRX2PZ2PphdlDt3V8OBJKYW1e835 1489173894 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 81B6C7E186; Fri, 10 Mar 2017 14:24:54 -0500 (EST) Subject: Re: Upgrading postmaster's log messages about bind/listen errors To: Tom Lane , Robert Haas References: <9564.1489091245@sss.pgh.pa.us> <19479.1489121003@sss.pgh.pa.us> Cc: Joe Conway , "pgsql-hackers@postgresql.org" From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Fri, 10 Mar 2017 14:24:54 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <19479.1489121003@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 3/9/17 23:43, Tom Lane wrote: > However, if we're measuring this on a scale of usefulness to the average > DBA, I would argue that it's of more interest than any of these messages > that currently appear by default: > > 2017-03-09 23:40:12.334 EST [19335] LOG: MultiXact member wraparound protections are now enabled > 2017-03-09 23:40:12.335 EST [19339] LOG: autovacuum launcher started > 2017-03-09 23:40:12.336 EST [19341] LOG: logical replication launcher started > > The first of those is surely past its sell-by date. As for the other two, > we should log *failure* to start, but not the normal case. I'm OK with removing these. No news is good news. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers