Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bE1q2-0007ML-6T for pgsql-docs@arkaria.postgresql.org; Fri, 17 Jun 2016 22:02:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bE1q1-0002H8-Gj for pgsql-docs@arkaria.postgresql.org; Fri, 17 Jun 2016 22:02:05 +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 1bE1q0-0002GT-FX for pgsql-docs@postgresql.org; Fri, 17 Jun 2016 22:02:04 +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 1bE1px-0001nj-0k for pgsql-docs@postgresql.org; Fri, 17 Jun 2016 22:02:03 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1bE1pv-0008NH-Si; Fri, 17 Jun 2016 18:01:59 -0400 Date: Fri, 17 Jun 2016 18:01:59 -0400 From: Bruce Momjian To: Alvaro Herrera Cc: PostgreSQL-documentation Subject: Re: Pg_upgrade and collation Message-ID: <20160617220159.GD19359@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: <20160617215154.GA140481@alvherre.pgsql> User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -3.3 (---) 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 Fri, Jun 17, 2016 at 05:51:54PM -0400, Alvaro Herrera wrote: > Bruce Momjian wrote: > > The attached patch documents that pg_upgrade requires old/new servers to > > use compatibile collation library versions as well. > > I think this is way too thin to be helpful: Well, this is a much larger issue than pg_upgrade, e.g. moving a data directory from one cluster to another with a different collation library version could also cause problems, and I don't know that is documented at all. If we want to go larger, we have to do this in a more central location. > > > --- 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. > > > > I think it would be useful to indicate what to do if they are not > compatible. The indexes don't work reliably. We don't document what happens if shared objects don't match either, but again, if we want to clarify this, we need to do it more centrally. Ideas? -- 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