Re: postgres startup failure
От | Tom Lane |
---|---|
Тема | Re: postgres startup failure |
Дата | |
Msg-id | 9224.1274391847@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: postgres startup failure (Matt Bartolome <mattxbart@gmail.com>) |
Ответы |
Re: postgres startup failure
|
Список | pgsql-general |
Matt Bartolome <mattxbart@gmail.com> writes: > gdb output... > DEBUG: ----------------------------------------- > DEBUG: invoking IpcMemoryCreate(size=32595968) > DEBUG: max_safe_fds = 980, usable_fds = 1000, already_open = 10 > Detaching after fork from child process 18310. > Detaching after fork from child process 18311. > Program exited with code 01. Huh. So it called exit(1) somewhere, without generating any error message first. That's pretty unfriendly. Try setting a breakpoint at exit(), and if you can get it to stop there, get a stack trace from that point. Dunno if you're familiar with gdb, but the quick way to do this is to say b exit and then the "run" command. It's possible that the attempt to set the breakpoint will fail because libc.so isn't loaded yet, in which case you need two steps: b main run ... when control stops at main: b exit continue regards, tom lane
В списке pgsql-general по дате отправления: