Craig Ringer <craig@postnewspapers.com.au> writes:
> On 03/08/10 23:37, David R Robison wrote:
>> 2010-08-03 15:34:01 GMT LOCATION: PostmasterMain,
>> .\src\backend\postmaster\postmaster.c:743
>> 2010-08-03 15:34:01 GMT DEBUG: 00000: TZ "US/Eastern" matches Windows
>> timezone "Eastern Daylight Time"
>> 2010-08-03 15:34:01 GMT LOCATION: identify_system_timezone,
>> .\src\timezone\pgtz.c:1088
>> 2010-08-03 11:34:01 EDT DEBUG: 00000: invoking
>> IpcMemoryCreate(size=37044224)
>> 2010-08-03 11:34:01 EDT LOCATION: CreateSharedMemoryAndSemaphores,
>> .\src\backend\storage\ipc\ipci.c:130
>> 2010-08-03 11:34:01 EDT DEBUG: 00000: max_safe_fds = 987, usable_fds =
>> 1000, already_open = 3
>> 2010-08-03 11:34:01 EDT LOCATION: set_max_safe_fds,
>> .\src\backend\storage\file\fd.c:479
>> 2010-08-03 11:34:02 EDT DEBUG: 00000: logger shutting down
>> 2010-08-03 11:34:02 EDT LOCATION: SysLoggerMain,
>> .\src\backend\postmaster\syslogger.c:446
> This is pretty odd. It seems to init shared memory OK, set up the fd
> limits, then exit.
Actually, the logger is launched after those two steps, so the fact that
we see anything at all from the logger is interesting. What it looks
like to me is that the postmaster crashed at some point after launching
syslogger. There is (not supposed to be) any exit path that wouldn't
have logged a complaint message, ergo it was a crash not intentional
exit. But just where it crashed is hard to tell from this.
regards, tom lane