Yeah, made me blink too. But you nailed it on the head... looking in
postgresql.conf shows me that syslog = 2, which means no standard out.
Seems that the behavior between the port for 7.3 and 7.4 has changed and
now they log to syslog by default. Now to figure out why syslog doesn't
appear to be logging anything...
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.
Thank you once again for your late night help!
Greg
Tom Lane wrote:
> Gregory Wood <gwood@ewebengine.com> writes:
>
>>... I've even gone so far as to:
>>postmaster -D /usr/local/pgsql/data
>>That was also run as the database superuser. Unfortunately it doesn't
>>produce anything, it immediately runs and exits with no error. At this
>>point I'd be happy with just an error message!
>
>
> [blink] It definitely shouldn't exit without an error message.
>
> One thought that comes to mind is that you might have configured
> postgresql.conf to report errors only to syslog and not to stderr.
> If so, look in the system logs, or undo that change and try the manual
> startup again.
>
> If that's not it, are you game to get out the debugger? Exiting
> without a message is a bug-that-needs-fixed, in my book.
>
> regards, tom lane
