| 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: | 2009-03-31 14:45:10 |
| Message-ID: | 200903311745.10605.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Pitt | 2009-04-01 06:24:14 | Re: shared_buffers/SHMMAX defaults? |
| Previous Message | Tom Lane | 2009-03-31 14:01:22 | Re: BUG #4743: potential bug between int and uint |