| After making this change, and increasing the max number of buffers to
| 128 and the max number of connections to 64, I rebooted my system.
| Things come up fine, Postgres seems happy, but shortly after the
| Postgres server dies or terminates with nothing in logs as to WHY it
| terminates and it keeps doing so even after I revert back to
I've been running Postgres on Solaris x86 (5.8 & 5.9) for several years
now and there's a few system level problems with Solaris' shared memory.
The shmmax you can set to almost any number without issue. But the
others, Solaris will produce kernel panics if the numbers are set too high.
I'd recommend only changing shminfo_shmmax at the start. (And make it a
larger number while you're at it. 128 shared_buffers is a grand total of
1MB of memory; Postgres will run dog slow at that setting. My servers
use settings of 16,000 for 512MB machines to 250,000 for 8GB machines.)
64 connections should not be a problem with the default Solaris shared
memory settings (at least not as far as I can remember). If it does
complain, then change only the variable the Postgres logs mention.