Re: 7.4.1 Server Not Starting?

From: Gregory Wood <gwood(at)ewebengine(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: 7.4.1 Server Not Starting?
Date: 2004-01-05 07:04:16
Message-ID: 3FF90C70.5060600@ewebengine.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> It's quite likely that the syslog daemon is configured to drop PG
> messages instead of logging them. This would be a rather unfortunate
> combination of default behaviors, however --- suggest griping to the
> respective package maintainers that they need to get on the same page.

It's logging to the local0 facility which isn't set up by default... I'm
surprised that the catch all /var/log/messages didn't catch it, but I'm
up hours late and can't remember what that defaulted to at the moment.
I'll try to remember to send that suggestion to the port maintainer.

>>I also found the source of the error: I had previously (7.3 again) set
>>max_fsm_relations = 10000. Apparently 7.4 doesn't like that too much.
>>Bumping that back to 1000 seems to do the trick.
>
> Hmm, maybe that's pushing our shared-memory request just beyond the
> kernel's SHMMAX? If so, again it'd be an unfortunate combination of
> default settings. max_fsm_relations = 10000 shouldn't take all that
> much more memory ...

Well, here are the relevant (?) settings I changed:
max_connections = 256
shared_buffers = 8192
max_fsm_relations = 10000
max_fsm_pages = 100000
sort_mem = 8192
vacuum_mem = 32768

Perhaps a combination of those settings is what did it?

Greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-01-05 07:08:44 Re: 7.4.1 Server Not Starting?
Previous Message Tom Lane 2004-01-05 06:48:05 Re: 7.4.1 Server Not Starting?