From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Problems tuning shared_buffers value |
Date: | 2003-03-20 15:14:12 |
Message-ID: | 23270.1048173252@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Bill Moran <wmoran(at)potentialtech(dot)com> writes:
> curious about some things, so I set shared_buffers to 16 (which the
> config file claims is the lowest allowable value) The result was
> that Postgre refused to start. I upped it to 32 and the result
> was the same.
> I looked in both /var/log/messages and in /usr/local/pgsql/logfile
> and found nothing about _why_ it wouldn't start,
There's something broken about your logging setup then, because the
postmaster will most definitely tell you why it's not starting:
$ postmaster -B 16
postmaster: The number of buffers (-B) must be at least twice the number of allowed connections (-N) and at least 16.
$ postmaster -B 32
postmaster: The number of buffers (-B) must be at least twice the number of allowed connections (-N) and at least 16.
$
Without having looked at the code, I think that these very-early-startup
messages may only get sent to stderr and not syslog; so take another
look at what you're doing with the postmaster's stderr.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Alberto Soto Cordones | 2003-03-20 15:18:53 | SQL question |
Previous Message | Bill Moran | 2003-03-20 13:06:51 | Problems tuning shared_buffers value |