Commit b7ded118 authored by Christoph Berg's avatar Christoph Berg

postgresql-common.NEWS: Warn users about glibc collation changes

The same message will appear in the release-notes: #926627
parent 3c8d0e14
Pipeline #43202 failed with stage
in 8 minutes and 17 seconds
postgresql-common (200+deb10u1) unstable; urgency=medium
* When upgrading from stretch to buster, all text indexes need to be
reindexed. Warn users about that in NEWS.Debian.
-- Christoph Berg <myon@debian.org> Fri, 12 Apr 2019 14:32:52 +0200
postgresql-common (200) unstable; urgency=medium
* pg_createcluster: Don't refuse explicit -p argument even when port is
......
postgresql-common (200+deb10u1) buster; urgency=high
Existing PostgreSQL databases need to be reindexed
When upgrading from stretch to buster, the glibc locale data is upgraded.
Specifically, this changes how PostgreSQL sorts data in text indexes. To
avoid corruption, such indexes need to be REINDEXed immediately after
upgrading the locales or locales-all packages, before putting back the
database into production.
Suggested command: sudo -u postgres reindexdb --all
Alternatively, upgrade the databases to PostgreSQL 11 using
pg_upgradecluster. (This uses pg_dump by default which will rebuild all
indexes. Using -m upgrade or pg_upgrade is not safe because it preserves
the now-wrong index ordering.)
Refer to the PostgreSQL Wiki for more information:
https://wiki.postgresql.org/wiki/Locale_data_changes
-- Christoph Berg <myon@debian.org> Fri, 12 Apr 2019 14:32:52 +0200
postgresql-common (161) unstable; urgency=medium
pg_ctlcluster is now enforcing stricter file ownership on the cluster config
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment