Your message dated Sun, 16 Oct 2022 17:15:55 +0200 with message-id <y0wgk9c9st9zu...@msg.df7cb.de> and subject line Re: Bug#1021074: postgresql-15: collation version mismatch warnings on upgrading to 15-rc1 has caused the Debian Bug report #1021074, regarding postgresql-15: collation version mismatch warnings on upgrading to 15-rc1 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 ow...@bugs.debian.org immediately.) -- 1021074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: postgresql-15 Version: 15~rc1-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I upgraded postgresql-15 from 15~beta4 to 15~rc1 and got a whole bunch of warnings, which surprised me and I don't know what to do with it. I've done the following on this database: - - Installed psql 14 - - Created a quassel DB+role and imported data into it - - Upgraded to psql 15 beta3 - - Dropped the quassel DB and recreated it (but it holds no data) - - Now the upgrade to psql 15 rc1 I have NOT done any configuration (changes) to the standard DBs I did have a libc6 upgrade from 2.34 to 2.35 in between and those versions match the details of the warnings. That may be a coincidence. The main part of the warnings, is this: WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. Full upgrade log: root@cs21:~# aptitude safe-upgrade ... Preparing to unpack .../20-postgresql-client-15_15~rc1-1_arm64.deb ... Unpacking postgresql-client-15 (15~rc1-1) over (15~beta4-1) ... Preparing to unpack .../21-postgresql-15_15~rc1-1_arm64.deb ... PostgreSQL 15 catalog version number changed from 202209011 to 202209061, checking for clusters using the old version ... Cluster 15/main is using catalog version 202209011 Saving binaries for PostgreSQL 15 catalog version 202209011 in /var/tmp/postgresql-15-202209011 ... Unpacking postgresql-15 (15~rc1-1) over (15~beta4-1) ... ... Setting up postgresql-15 (15~rc1-1) ... Cluster 15 main needs upgrading due to catalog version change: pg_renamecluster 15 main main.old pg_upgradecluster 15 main.old --rename main -m upgrade --old-bindir=/var/tmp/postgresql-15-202209011/bin pg_dropcluster 15 main.old rm -rf /var/tmp/postgresql-15-202209011 Setting up libqt5sql5-sqlite:arm64 (5.15.6+dfsg-2) ... Processing triggers for man-db (2.10.2-3) ... Processing triggers for postgresql-common (243) ... Building PostgreSQL dictionaries from installed myspell/hunspell packages... Removing obsolete dictionary files: Processing triggers for debianutils (5.7-0.3) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for libc-bin (2.35-1) ... root@cs21:~# pg_renamecluster 15 main main.old root@cs21:~# pg_upgradecluster 15 main.old --rename main -m upgrade --old-bindir=/var/tmp/postgresql-15-202209011/bin Restarting old cluster with restricted connections... Notice: extra pg_ctl/postgres options given, bypassing systemctl for start operation WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. Stopping old cluster... Creating new PostgreSQL cluster 15/main ... /usr/lib/postgresql/15/bin/initdb -D /var/lib/postgresql/15/main --auth-local peer --auth-host scram-sha-256 --no-instructions --encoding UTF8 --lc-collate en_US.utf8 --lc-ctype en_US.utf8 The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with this locale configuration: provider: libc LC_COLLATE: en_US.utf8 LC_CTYPE: en_US.utf8 LC_MESSAGES: en_US.UTF-8 LC_MONETARY: en_US.UTF-8 LC_NUMERIC: en_US.UTF-8 LC_TIME: en_US.UTF-8 The default text search configuration will be set to "english". Data page checksums are disabled. fixing permissions on existing directory /var/lib/postgresql/15/main ... ok creating subdirectories ... ok selecting dynamic shared memory implementation ... posix selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... Europe/Amsterdam creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok syncing data to disk ... ok Copying old configuration files... Copying old start.conf... Copying old pg_ctl.conf... /usr/lib/postgresql/15/bin/pg_upgrade -b /var/tmp/postgresql-15-202209011/bin -B /usr/lib/postgresql/15/bin -p 5432 -P 5432 -d /etc/postgresql/15/main.old -D /etc/postgresql/15/main Finding the real data directory for the source cluster ok Finding the real data directory for the target cluster ok Performing Consistency Checks - ----------------------------- Checking cluster versions ok WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "postgres" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "quassel" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE quassel REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "postgres" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "quassel" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE quassel REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. Checking database user is the install user ok Checking database connection settings WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. ok WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. Checking for prepared transactions ok Checking for system-defined composite types in user tables WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "postgres" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "quassel" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE quassel REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. ok Checking for reg* data types in user tables WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "postgres" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "quassel" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE quassel REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. ok Checking for contrib/isn with bigint-passing mismatch ok Creating dump of global objects ok Creating dump of database schemas ok Checking for presence of required libraries ok Checking database user is the install user ok Checking for prepared transactions ok Checking for new cluster tablespace directories ok If pg_upgrade fails after this point, you must re-initdb the new cluster before continuing. Performing Upgrade - ------------------ Analyzing all rows in the new cluster ok Freezing all rows in the new cluster ok Deleting files from new pg_xact ok Copying old pg_xact to new server ok Setting oldest XID for new cluster ok Setting next transaction ID and epoch for new cluster ok Deleting files from new pg_multixact/offsets ok Copying old pg_multixact/offsets to new server ok Deleting files from new pg_multixact/members ok Copying old pg_multixact/members to new server ok Setting next multixact ID and offset for new cluster ok Resetting WAL archives ok Setting frozenxid and minmxid counters in new cluster ok Restoring global objects in the new cluster ok Restoring database schemas in the new cluster ok WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "postgres" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "quassel" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE quassel REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. Copying user relation files ok Setting next OID for new cluster ok Sync data directory to disk ok Creating script to delete old cluster ok WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. Checking for extension updates WARNING: database "template1" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "postgres" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. WARNING: database "quassel" has a collation version mismatch DETAIL: The database was created using collation version 2.34, but the operating system provides version 2.35. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE quassel REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. ok Upgrade Complete - ---------------- Optimizer statistics are not transferred by pg_upgrade. Once you start the new server, consider running: /usr/lib/postgresql/15/bin/vacuumdb --all --analyze-in-stages Running this script will delete the old cluster's data files: ./delete_old_cluster.sh pg_upgrade output scripts are in /var/log/postgresql/pg_upgradecluster-15-15-main.xg1u Disabling automatic startup of old cluster... Success. Please check that the upgraded cluster works. If it does, you can remove the old cluster with pg_dropcluster 15 main.old Ver Cluster Port Status Owner Data directory Log file 15 main.old 5432 down postgres /var/lib/postgresql/15/main.old /var/log/postgresql/postgresql-15-main.old.log Ver Cluster Port Status Owner Data directory Log file 15 main 5432 down postgres /var/lib/postgresql/15/main /var/log/postgresql/postgresql-15-main.log root@cs21:~# pg_dropcluster 15 main.old root@cs21:~# rm -rf /var/tmp/postgresql-15-202209011 I realize I'm running pre-release software, so it may be harmless and nothing to do about it, in which case feel free to close this bug. - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 5.19.0-2-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postgresql-15 depends on: ii debconf [debconf-2.0] 1.5.79 ii libc6 2.35-1 ii libgcc-s1 12.2.0-3 ii libgssapi-krb5-2 1.20-1 ii libicu71 71.1-3 ii libldap-2.5-0 2.5.13+dfsg-2 ii libllvm14 1:14.0.6-2 ii liblz4-1 1.9.4-1 ii libpam0g 1.5.2-2 ii libpq5 15~rc1-1 ii libselinux1 3.4-1+b2 ii libssl3 3.0.5-4 ii libstdc++6 12.2.0-3 ii libsystemd0 251.4-3 ii libuuid1 2.38.1-1 ii libxml2 2.9.14+dfsg-1+b1 ii libxslt1.1 1.1.35-1 ii libzstd1 1.5.2+dfsg-1 ii locales 2.35-1 ii postgresql-client-15 15~rc1-1 ii postgresql-common 243 ii ssl-cert 1.1.2 ii tzdata 2022d-1 ii zlib1g 1:1.2.11.dfsg-4.1 Versions of packages postgresql-15 recommends: ii sysstat 12.5.6-1 postgresql-15 suggests no packages. - -- debconf information: postgresql-15/postrm_purge_data: true -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCYzhMXgAKCRDXblvOeH7b blqHAP9TdophrEdsI3anwcjDWv3+qUquRQVq2ZGGRW5zzV0khQD+Iqrb755HN/s8 Z1jbDxkM3UI4edsFPyQcy0Xd+7fRKgM= =e6h0 -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---Re: Diederik de Haas > On zaterdag 1 oktober 2022 16:19:19 CEST you wrote: > > The main part of the warnings, is this: > > WARNING: database "template1" has a collation version mismatch > > DETAIL: The database was created using collation version 2.34, but the > > operating system provides version 2.35. > > HINT: Rebuild all objects in this database that use the default collation > > and run ALTER DATABASE template1 REFRESH COLLATION VERSION, > > or build PostgreSQL with the right library version. > > As I didn't know how to fix that issue and didn't know what kind of effect it > would have when I'd put actual data in the DBs, I purged all the postgresql > packages and installed them anew. Hi Diederik, that's https://www.postgresql.org/docs/15/sql-altercollation.html#SQL-ALTERCOLLATION-NOTES in action. I'm not aware of any differences between these libc versions, so just running "alter databse refresh collation version" would have been enough. Christoph
--- End Message ---
