Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Database migration across different operating systems
From: Natalie Wenz <nataliewenz@gmail.com>
In-Reply-To: <875zuzr06z.fsf@news-spur.riddles.org.uk>
Date: Tue, 8 Jan 2019 13:16:47 -0600
Cc: pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC1500C0-AD6C-45E6-8E97-6A8709A5DF58@gmail.com>
References: <A740E5D2-34BE-46AA-A9FE-50F510E771EC@gmail.com>
 <875zuzr06z.fsf@news-spur.riddles.org.uk>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
Precedence: bulk

Thanks, Andrew.=20

All of our databases do have lc_collate=3DC. To check my understanding, if t=
hat were not the case, we=E2=80=99d need to reindex, but since it is all lc_=
collate=3DC, we shouldn=E2=80=99t run into that particular problem. Did I ge=
t that right?=20

On Jan 8, 2019, at 3:06 AM, Andrew Gierth <andrew@tao11.riddles.org.uk> wrot=
e:

>>>>>> "Natalie" =3D=3D Natalie Wenz <nataliewenz@gmail.com> writes:
>=20
> Natalie> We are in an unusual circumstance, where we need to move all
> Natalie> of our Postgres 10 databases from their homes on servers
> Natalie> running FreeBSD 11 with ZFS to servers in another data center
> Natalie> running Red Hat Linux 7.6 (also with ZFS), with minimal
> Natalie> downtime.
>=20
> [...]
>=20
> Natalie> We=E2=80=99ve tested this procedure on a small database, and it
> Natalie> starts, it runs, returns queries. There seems to be no issues.
>=20
> Natalie> Is this a reasonable approach? Are there any known
> Natalie> concerns/things to investigate before choosing this course?
>=20
> Locales will bite you unless your databases all have lc_collate=3DC or
> you're using ICU for all collations); you will need, at minimum, to
> reindex every index containing a collatable column with an OS-provided
> collation (i.e. not ICU and not C / POSIX).
>=20
> --=20
> Andrew (irc:RhodiumToad)