[Pkg-postgresql-public] Bug#784005: postgresql-9.4: Cluster upgrade from 9.1 to 9.4 results in broken configuration
Christoph Berg
myon at debian.org
Sat May 16 08:11:30 UTC 2015
Re: Gunnar Wolf 2015-05-15 <20150515035332.GA62327 at gwolf.org>
> Christoph Berg dijo [Thu, May 14, 2015 at 10:11:44PM +0200]:
> > Hi Gunnar,
> >
> > I'd call it a LXC bug if it doesn't support POSIX shared memory.
> > That said, I've been bitten by this problem as well - in my case,
> > /dev/shm was simply not mounted and a cluster with no explicit
> > dynamic_shared_memory_type setting defaulted to "posix" didn't start.
> > If you create a new cluster in such an environment, initdb will probe
> > the various shared memory types and pick one that works. I'm not
> > really happy with this auto-probing because it hides the real problem,
> > but atm that's what upstream has designed.
> >
> > We'll document the gotcha in README.Debian.
>
> Hi!
>
> I asked a PostgreSQL developer friend of mine, and he answered (in
> Spanish, translation bugs are mine):
>
> Hmm, if I understand correctly, the problem is that the
> postgresql.conf is copied from the old server to the new one,
> right? I think that, by itself, is a bug... The configuration
> files are attempted to be kept reasonably compatible, but there is
> no promise that it will always work.
Hi Gunnar,
of course pg_upgrade takes care of upgrading any non-compatible old
settings to new ones (or removing them).
> Particularly, with parameters such as the shared memory type,
> initdb should take care of setting the right values.
>
> I think it's a pg_upgradecluster bug (which is part of the Debian
> packaging, not of Postgres)
After sleeping over it, I think we should indeed make
pg_upgradecluster add some dynamic_shared_memory_type parameter to the
old config file.
Fwiw, the first complaints about the upstream part of the problem are
from exactly one year ago...
http://www.postgresql.org/message-id/CAOtHd0A5KQHL5Zv9V0c9i98i7otuwOhk=PM3grxuUgh4TR3JPA@mail.gmail.com
> I guess LXC does provide shared memory, but it might be that my
> configuration does not allow it. I am newbie-ish on its specifics.
Christoph
--
cb at df7cb.de | http://www.df7cb.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20150516/3f2d2356/attachment.sig>
More information about the Pkg-postgresql-public
mailing list