Date: Fri, 10 Mar 2017 17:27:22 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Euler Taveira <euler@timbira.com.br>,
	Robert Haas <robertmhaas@gmail.com>,
	Joe Conway <mail@joeconway.com>,
	"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: Upgrading postmaster's log messages about bind/listen
 errors
Message-ID: <20170310202722.shpauoi6zcpptu2k@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <15080.1489177388@sss.pgh.pa.us>
User-Agent: NeoMutt/20170206-195-7adf12 (1.7.2)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Tom Lane wrote:
> Euler Taveira <euler@timbira.com.br> writes:
> > 2017-03-10 1:43 GMT-03:00 Tom Lane <tgl@sss.pgh.pa.us>:
> >> 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.

Well, you could take a broken 9.3 installation and pg_upgrade it to
pg10.  It wouldn't be any less broken.

There's still people running buggy 9.3 releases, as we see in these
lists every now and then.

-- 
Álvaro Herrera                https://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