Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cmR4G-0002tE-Ox for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2017 20:23:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cmR4G-0007Sv-5F for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Mar 2017 20:23:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cmR4F-0007Sm-L0 for pgsql-hackers@postgresql.org; Fri, 10 Mar 2017 20:23:15 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cmR4C-0006Qa-S4 for pgsql-hackers@postgresql.org; Fri, 10 Mar 2017 20:23:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v2AKN8e7015081; Fri, 10 Mar 2017 15:23:08 -0500 From: Tom Lane To: Euler Taveira cc: Robert Haas , Joe Conway , "pgsql-hackers@postgresql.org" Subject: Re: Upgrading postmaster's log messages about bind/listen errors In-reply-to: References: <9564.1489091245@sss.pgh.pa.us> <19479.1489121003@sss.pgh.pa.us> Comments: In-reply-to Euler Taveira message dated "Fri, 10 Mar 2017 13:17:33 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15079.1489177388.1@sss.pgh.pa.us> Date: Fri, 10 Mar 2017 15:23:08 -0500 Message-ID: <15080.1489177388@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 Euler Taveira writes: > 2017-03-10 1:43 GMT-03:00 Tom Lane : >> 2017-03-09 23:40:12.334 EST [19335] LOG: MultiXact member wraparound >> protections are now enabled > It should be DEBUG1 as soon as 9.3 is deprecated. Uh, what's that got to do with it? I'm not proposing to downgrade this message in 9.3, or indeed any current release branch. But it's hard to believe that a 9.3 installation that had the problem would manage to make it all the way to a v10 upgrade without the problem having been fixed. Even if there's one or two incompetent DBAs out there whom that would apply to, I don't think the rest of the world needs to keep seeing this message by default. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers