[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#927129: marked as done (unblock: postgresql-common/200+deb10u1)



Your message dated Mon, 15 Apr 2019 12:45:00 +0000
with message-id <af4c2c4b-4c99-e4b2-39c9-9f8dad66a8b7@thykier.net>
and subject line Re: Bug#927129: unblock: postgresql-common/200+deb10u1
has caused the Debian Bug report #927129,
regarding unblock: postgresql-common/200+deb10u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
927129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927129
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package postgresql-common. The new version contains in
NEWS.Debian the same message that was added to the release notes as
#926627. Thanks.

commit b7ded1188f8605fc815149018d44766d2c302bd2
Author: Christoph Berg <christoph.berg@credativ.de>
Date:   Fri Apr 12 15:18:36 2019 +0200

    postgresql-common.NEWS: Warn users about glibc collation changes
    
    The same message will appear in the release-notes: #926627

diff --git a/debian/changelog b/debian/changelog
index 58f61b0..427c1d8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+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
diff --git a/debian/postgresql-common.NEWS b/debian/postgresql-common.NEWS
index fca02fd..7db0799 100644
--- a/debian/postgresql-common.NEWS
+++ b/debian/postgresql-common.NEWS
@@ -1,3 +1,25 @@
+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

unblock postgresql-common/200+deb10u1

Christoph

--- End Message ---
--- Begin Message ---
Christoph Berg:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock package postgresql-common. The new version contains in
> NEWS.Debian the same message that was added to the release notes as
> #926627. Thanks.
> 
> [...]
> 
> unblock postgresql-common/200+deb10u1
> 
> Christoph
> 

Unblocked, thanks.
~Niels

--- End Message ---

Reply to: