Hello fellow PostgreSQL packagers, recently, I started to get quite a bunch of bug reports a la "PostgreSQL fails to start due to too little shared memory" [1]. I have never seen this before, neither in Debian, so I guess the SHMMAX defaults changed somewhat in Linux 2.6.27. It seems that with other components, such as X.org, using large amounts of shared memory as well, startup sometimes works and sometimes doesn't.
Now I wonder what I should do about it. I see these options:
(1) Ignore
+ no hidden magic
- very inconvenient, package installation does not create default
cluster sometimes, or the default cluster fails to start on
system boot
Best solution for admin control freaks.
(2) Be more conservative about initdb's default setting
+ no hidden magic
+ upstream compatible solution
- suboptimal performance by default
(3) Change SHMMAX in postgresql's init script if necessary
+ Always works
- Unexpected, works behind admin's back.
Currently I tend towards (2), but I'd like to hear some more opinions
about it.
Does anyone else have seen this problem as well?
Thanks,
Martin
[1] https://launchpad.net/bugs/264336
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
