Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: shared_buffers/SHMMAX defaults?
- From: Peter Eisentraut <peter_e(at)gmx(dot)net>
- To: pgsql-bugs(at)postgresql(dot)org
- Cc: Martin Pitt <mpitt(at)debian(dot)org>
- Subject: Re: shared_buffers/SHMMAX defaults?
- Date: Tue, 31 Mar 2009 17:45:10 +0300
- Message-id: <200903311745.10605.peter_e@gmx.net> <text/plain>
On Monday 30 March 2009 17:34:36 Martin Pitt wrote: > 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. I think this calls for a distribution-specific policy. E.g., why shouldn't X be forced to use a "more conservative setting"? How do we even know how much memory X will use today or tomorrow, or whether X is installed or will be installed?
- References:
- shared_buffers/SHMMAX defaults?
- From: Martin Pitt
- shared_buffers/SHMMAX defaults?
- Prev by Date: Re: BUG #4743: potential bug between int and uint
- Previous by thread: Re: shared_buffers/SHMMAX defaults?
- Next by thread: BUG #4742: wrong resultset instead of syntax error
- Indexes: