Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cfwcM-0001HX-7D for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Feb 2017 22:39:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cfwcL-0007ZX-QS for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Feb 2017 22:39:37 +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 1cfwaw-0005lc-Eu for pgsql-hackers@postgresql.org; Mon, 20 Feb 2017 22:38:10 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cfwat-0002Zl-Tt for pgsql-hackers@postgresql.org; Mon, 20 Feb 2017 22:38:09 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1cfwar-0000tS-SP; Mon, 20 Feb 2017 17:38:05 -0500 Date: Mon, 20 Feb 2017 17:38:05 -0500 From: Bruce Momjian To: Peter Geoghegan Cc: Peter Eisentraut , Thomas Munro , pgsql-hackers Subject: Re: ICU integration Message-ID: <20170220223805.GD2672@momjian.us> References: <85364fde-091f-bbc0-fec2-e3ede39840a6@2ndquadrant.com> <3a88fa29-275b-f547-9957-86d4b2cd68db@2ndquadrant.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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 On Wed, Feb 15, 2017 at 10:35:34PM -0800, Peter Geoghegan wrote: > On Wed, Feb 15, 2017 at 9:17 PM, Peter Eisentraut > wrote: > > Stable operating systems shouldn't do major library upgrades, so I feel > > pretty confident about this. > > There is one case where it *is* appropriate for a bugfix release of > ICU to bump collator version: When there was a bug in the collator > itself, leading to broken binary blobs [1]. We should make the user > REINDEX when this happens. > > I think that ICU may well do this in point releases, which is actually > a good thing. So, it seems like a good idea to test that there is no > change, in a place like check_strxfrm_bug(). In my opinion, we should > LOG a complaint in the event of a mismatch rather than refusing to > start the server, since there probably isn't that much chance of the > user being harmed by the bug. The cost of not starting the server > properly until a REINDEX finishes or similar looks particularly > unappealing when one considers that the app was probably affected by > any corruption for weeks or months before the ICU update enabled its > detection. > http://www.postgresql.org/mailpref/pgsql-hackers I can't think of any cases where we warn of possible corruption only in the server logs. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers