The referred page is here: https://pmg.proxmox.com/wiki/index.php/Upgrade_from_5.x_to_6.0
If somebody can edit this page, please add the detail REINDEX cmd at "Upgrade_postgres_Database" section.
As a newbie, in the upgrade process, I don't know how to REINDEX the old database. I just learn from the system inform email
about "udo -u postgres reindexdb --all".
================================================================================
From: root <root@mailgate.xyz.com>
Subject: apt-listchanges: news for mailgate
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
================================================================================
If somebody can edit this page, please add the detail REINDEX cmd at "Upgrade_postgres_Database" section.
As a newbie, in the upgrade process, I don't know how to REINDEX the old database. I just learn from the system inform email
about "udo -u postgres reindexdb --all".
================================================================================
From: root <root@mailgate.xyz.com>
Subject: apt-listchanges: news for mailgate
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
================================================================================
