Control: tags -1 moreinfo Re: Michael Braun 2016-05-30 <20160530093300.28637.79724.report...@flow-campus-01.fem.tu-ilmenau.de> > * What led up to the situation? > > I'm running unattended-upgrade which recently upgraded the locales package. > That triggered running locale-gen, and the problem also appears when running > locale-gen alone.
Hi, I've just tried to reproduce the problem here, but things just work for me. What I did was to install postgresql-9.1 9.1.22-0+deb7u1, start it on a de_DE.utf8 cluster, and then upgrade locales from 2.13-38+deb7u9 to 2.13-38+deb7u11. The database was working as before, without requiring a restart. Even upgrading libc6+dependencies doesn't break it. Does that match what you were doing? (I see that you seem to have LC_ALL set, that might complicate matters.) > Manually restarting postgresql "fixes" the issue for me. What other packages were upgraded there? The generic answer here is likely that if any of the low-level libc packages are upgraded (which might include locales), a database restart is required. I don't see that we can fix this on the PostgreSQL side. > $ localedef --no-archive -f UTF-8 -i en_US en_US.UTF-8 > > But this really should not be needed as I guess it will not become updated > automatically. I'd additionally claim that unattended upgrades might be a bad idea. (Note that in jessie, libc upgrades will ask you to restart PostgreSQL. Unless I'm mistaken, in wheezy, that logic wasn't present yet.) Christoph
signature.asc
Description: PGP signature
_______________________________________________ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
