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

From jseymour@LinxNet.com (Jim Seymour)
Subject Re: Solaris initdb fails: shmmax tweak alternative?
Date
Msg-id 20040406143334.185394307@jimsun.LinxNet.com
Whole thread Raw
In response to Solaris initdb fails: shmmax tweak alternative?  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-hackers
> 
> Anyone see a benefit of adding command line flags to initdb to force
> lower shared memory use without require a recompile?
[snip]
> 

When I built and installed pgsql at work, on a production server,
I ran into the shared memory problem.  I wanted to fire pgsql up
*right* *away*, to begin testing and so-on, so I hacked the shell
script.

Early next morning I rebooted the server, with the shared memory
changes already configured.

So yes: I can see a certain limited set of conditions under which
doing such a thing might be useful.

Jim


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: union vs. sort
Next
From: "Magnus Hagander"
Date:
Subject: Re: Function to kill backend