Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bI1N1-0008AC-Vw for pgsql-docs@arkaria.postgresql.org; Tue, 28 Jun 2016 22:20:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bI1N0-0000UM-Hv for pgsql-docs@arkaria.postgresql.org; Tue, 28 Jun 2016 22:20:38 +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 1bI1Me-0008VT-Gq for pgsql-docs@postgresql.org; Tue, 28 Jun 2016 22:20:16 +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 1bI1Mb-0004Qa-JK for pgsql-docs@postgresql.org; Tue, 28 Jun 2016 22:20:15 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1bI1MZ-0005CV-Av; Tue, 28 Jun 2016 18:20:11 -0400 Date: Tue, 28 Jun 2016 18:20:11 -0400 From: Bruce Momjian To: Peter Geoghegan Cc: Alvaro Herrera , PostgreSQL-documentation Subject: Re: Pg_upgrade and collation Message-ID: <20160628222011.GD11193@momjian.us> References: <20160617154311.GB19359@momjian.us> <20160617215154.GA140481@alvherre.pgsql> 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: -3.2 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Tue, Jun 28, 2016 at 02:58:58PM -0700, Peter Geoghegan wrote: > On Fri, Jun 17, 2016 at 2:51 PM, Alvaro Herrera > wrote: > > I think this is way too thin to be helpful: > > > >> --- 61,68 ---- > >> checking for compatible compile-time settings, including 32/64-bit > >> binaries. It is important that > >> any external modules are also binary compatible, though this cannot > >> ! be checked by pg_upgrade. Compatible collation > >> ! library versions must also be used. > >> > > Unfortunately, the reality is that as things stand, there is no way to > test compatibility on all platforms. Glibc does have a notion of > collation versioning, though [1]. Yes, the patch text is clearly weasel-words in that we can't explain how to detect incompatible. > I have long advocated adopting ICU as our defacto standard "collation > provider", primarily so that we can directly control collations and > collation versioning. I think that doing this would solve many > problems. Besides, even SQLite has optional ICU support. PostgreSQL is > the only major database system that I'm aware of that relies on > operating system collations exclusively. I am hopeful ICU has improved enough since we last researched that support for it will soon be added. -- 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-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs