On Sat, Jul 2, 2016 at 01:22:48PM -0400, Bruce Momjian wrote:
> On Sat, Jul 2, 2016 at 06:02:12PM +0200, Christoph Berg wrote:
> > Re: Bruce Momjian 2016-07-02 <[email protected]>
> > > > Shouldn't this mention that OS upgrades are a possible problem as
> > > > well? We've seen the de_DE.UTF-8 ordering break in RHEL 5->6, and
> > > > again in 6->7. (5 and 7 are compatible.) The problematic strings were
> > > > "999" and "9-9-9".
> > >
> > > Yes, we can do that. Do you have suggested wording? I was not sure how
> > > to tell people anything related to collation versions.
> >
> > How about simply this: ?
> >
> > 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
> > eason,
> > a cluster cannot switch to an incompatible collation library
> > ersion,
> > either through
> >
> > + operating system upgrade,
> >
> > snapshot restore, binary streaming replication, or
> > <application>pg_upgrade</> run.
>
> OK, good point. I was more focused on cluster moves than an OS change.
> How is the attached patch?
With the mention of different operating systems, there is no need to
mention pg_upgrade anymore as it is already covered. Updated 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 e3e254b..4e233b0
*** a/doc/src/sgml/runtime.sgml
--- b/doc/src/sgml/runtime.sgml
***************
*** 1,4 ****
! <!-- doc/src/sgml/runtime.sgml -->
<chapter id="runtime">
<title>Server Setup and Operation</title>
--- 1,4 ----
! `<!-- doc/src/sgml/runtime.sgml -->
<chapter id="runtime">
<title>Server Setup and Operation</title>
*************** postgres$ <userinput>initdb -D /usr/loca
*** 188,195 ****
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">
--- 188,195 ----
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, a
! different operating system, or an operating system upgrade.
</para>
<sect2 id="creating-cluster-mount-points">
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
