On Sun, Jan 29, 2023 at 02:03:05PM +0100, Diederik de Haas wrote: > On Tue, 24 Jan 2023 10:22:28 +0000 Julian Gilbey <j...@debian.org> wrote: > > Package: postgresql-15 > > Version: 15.1-1+b1 > > > > I recently started getting warnings such as the following from my > > postgresql backup script: > > > > WARNING: database "postgres" has a collation version mismatch > > DETAIL: The database was created using collation version 2.35, but > > the operating system provides version 2.36. > > 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. > > > > I don't know exactly where the source of this problem is, and there's > > no guidance as to how to fix it; for example, how do I rebuild all the > > objects in the database that use the default collation? > > The fix is in the HINT and you just need to run that command: > ALTER DATABASE postgres REFRESH COLLATION VERSION
Thanks! The messages were significantly more verbose than that (they also talked about rebuilding indexes and the like), so I didn't want to run this command without knowing it was safe to do so. > The cause for that (IIUC) is that the database was created when libc6 was at > version 2.35 and it has since been upgraded to 2.36. > > See also https://bugs.debian.org/1021074 > > > Something in a NEWS file or in README.Debian giving guidance would be > > very helpful here. > > A (major) libc6 upgrade is not something that will happen on Stable, so this > issue may only occur with people running Testing or Unstable. > OTOH: There are now (at least) 2 people who ran into it and didn't know what > to do with/about it. But it will happen when people upgrade their stable machines to bookworm once it is released. Best wishes, Julian
