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 <[email protected]> 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 +
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$ <userinput>initdb -D /usr/loca
*** 183,188 ****
--- 183,197 ----
locale setting. For details see <xref linkend="multibyte">.
</para>
+ <para>
+ Non<literal>C</> and and non-<literal>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
+ <application>pg_upgrade</> run.
+ </para>
+
<sect2 id="creating-cluster-mount-points">
<title>Use of Secondary File Systems</title>
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
