From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Problems tuning shared_buffers value |
Date: | 2003-03-20 15:27:09 |
Message-ID: | 3E79DDCD.7080104@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom Lane wrote:
> 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.
Ahhhh ... The startup script that the FreeBSD ports install redirects it
to /var/log/pgsql, which I hadn't noticed.
And I see the exact error messages you describe.
Thanks, Tom.
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Alberto Soto Cordones | 2003-03-20 16:32:22 | HELP |
Previous Message | Mario Alberto Soto Cordones | 2003-03-20 15:18:53 | SQL question |