[Pkg-postgresql-public] Bug#825814: postgresql-9.1: postgresql refuses connection with setlocale error after localgen is run

Christoph Berg myon at debian.org
Mon May 30 10:33:47 UTC 2016


Control: tags -1 moreinfo

Re: Michael Braun 2016-05-30 <20160530093300.28637.79724.reportbug at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20160530/2e3e606d/attachment.sig>


More information about the Pkg-postgresql-public mailing list