Solaris initdb fails: shmmax tweak alternative? - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Solaris initdb fails: shmmax tweak alternative?
Date
Msg-id 796a68cd608ee6160598d0a9bcfa6df8@biglumber.com
Whole thread Raw
Responses Re: Solaris initdb fails: shmmax tweak alternative?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Solaris initdb fails: shmmax tweak alternative?  (Jeff Trout <jeff@jefftrout.com>)
Re: Solaris initdb fails: shmmax tweak alternative?  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am trying to get version 7.4.2 installed on a Solaris box, but
initdb fails because of shmmax being set too low. It does this
even though initdb drops shared buffers as low as it can go (50).
Is there any other way of getting around this limitation? I know
that 50 is pretty low, but the recommended way (changing shmmax)
involves rebooting a production machine and, while possible, is
not preferred. (This is for a very small database, and having a
very low shared buffers is acceptable.)
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200404041539
-----BEGIN PGP SIGNATURE-----
iD8DBQFAcGUZvJuQZxSWSsgRAlNbAKCPBix3GX3M5LoOaF+uGSeNtaEKLgCfR5vV
zbN3wrnnbAAk3lkG2XH69fM=
=6lom
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: "Magnus Hagander"
Date:
Subject: serial vs parallell regression tests
Next
From: Tom Lane
Date:
Subject: Re: Function to kill backend