From ae09e15ef846b4b5b7664f375d31a2e635585aa6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Mon, 6 May 2024 03:48:40 +0200 Subject: Adding debian version 200+deb10u5. Signed-off-by: Daniel Baumann --- debian/postgresql-common.NEWS | 69 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 69 insertions(+) create mode 100644 debian/postgresql-common.NEWS (limited to 'debian/postgresql-common.NEWS') diff --git a/debian/postgresql-common.NEWS b/debian/postgresql-common.NEWS new file mode 100644 index 0000000..7db0799 --- /dev/null +++ b/debian/postgresql-common.NEWS @@ -0,0 +1,69 @@ +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 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 + when invoked as root, including operation via the init.d script or the + systemd unit: + + The postgresql.conf owner needs match the data directory owner, or the + postgresql.conf file needs to be owned by root. + + Default setups are not affected by this change. + + -- Christoph Berg Fri, 05 Sep 2014 15:48:13 +0200 + +postgresql-common (159) unstable; urgency=low + + PostgreSQL clusters managed by postgresql-common are now systemd enabled. For + each cluster, a service "postgresql@-" is created that can be + started/stopped/restarted/reloaded. A parent service "postgresql" acts on + all installed (start.conf has "auto") clusters in parallel like the init.d + script used to do. /etc/init.d/postgresql can still be used, though the mode + of starting individual versions ("/e/i/p start 9.3") no longer works. + + pg_ctlcluster can be used to control clusters, but for start and restart the + operation via systemd (using systemctl or the init.d script) is preferred, or + else the clusters will not run in cgroups. (Unfortunately this requires + root.) + + If the system is not running systemd, nothing changes. + + -- Christoph Berg Fri, 18 Jul 2014 23:52:09 +0300 + +postgresql-common (158) experimental; urgency=medium + + This postgresql-common release introduces several changes in the defaults + used for newly created database clusters, all configurable in + /etc/postgresql-common/createcluster.conf: + + * The default log_line_prefix is now '%t [%p-%l] %q%u@%d ' instead of '%t '. + * stats_temp_directory aka pg_stat_tmp is set to a subdirectory of + /var/run/postgresql by default. + * The use of SSL by default is (pre-)configurable via debconf and + createcluster.conf. + + If the logging_collector or syslog is being used, pg_lsclusters will show + the filename (or "syslog") instead of just "custom" in the Log file column. + + -- Christoph Berg Sat, 05 Jul 2014 16:40:16 +0200 -- cgit v1.2.3