Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bI0SD-0005bM-8V for pgsql-docs@arkaria.postgresql.org; Tue, 28 Jun 2016 21:21:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bI0SC-00009j-R6 for pgsql-docs@arkaria.postgresql.org; Tue, 28 Jun 2016 21:21:56 +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 1bI0SB-00008s-Ns for pgsql-docs@postgresql.org; Tue, 28 Jun 2016 21:21:55 +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 1bI0S9-0003GO-04 for pgsql-docs@postgresql.org; Tue, 28 Jun 2016 21:21:54 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1bI0S7-00030v-La; Tue, 28 Jun 2016 17:21:51 -0400 Date: Tue, 28 Jun 2016 17:21:51 -0400 From: Bruce Momjian To: Alvaro Herrera Cc: PostgreSQL-documentation Subject: Re: Pg_upgrade and collation Message-ID: <20160628212151.GC11193@momjian.us> References: <20160617220935.GF19359@momjian.us> <20160617221158.GA143199@alvherre.pgsql> <20160620151636.GB26992@momjian.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <20160620151636.GB26992@momjian.us> 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 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jun 20, 2016 at 11:16:36AM -0400, Bruce Momjian wrote: > In looking at the docs, it seems it would go in the Backup section > somewhere: > > https://www.postgresql.org/docs/9.6/static/backup.html > > Seems it would apply to both of these backup sections: > > 24.2. File System Level Backup > 24.3. Continuous Archiving and Point-in-Time Recovery (PITR) > > and also here: > > 25.2. Log-Shipping Standby Servers > > It seems odd to put it in all of these places, but where can we > centrally put it? In looking at the docs, I found that the section "Creating a Database Cluster", which covers initdb and collations, as the best place to put this warning. Patch attached. -- 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 + --Qxx1br4bt0+wmkIi Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="collation.diff" diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml new file mode 100644 index 4a0e35a..6d39ce7 *** a/doc/src/sgml/runtime.sgml --- b/doc/src/sgml/runtime.sgml *************** postgres$ initdb -D /usr/loca *** 183,188 **** --- 183,197 ---- locale setting. For details see . + + NonC and and non-POSIX locales rely on the + operating system's collation library for character set ordering. + This controls the ordering of keys stored in indexes. For this reason, + a cluster cannot switch to an incompatible collation library version, + either through snapshot restore, binary streaming replication, or + pg_upgrade run. + + Use of Secondary File Systems --Qxx1br4bt0+wmkIi Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs --Qxx1br4bt0+wmkIi--