Re: BUG #2195: log_min_messages crash server when in DEBUG3 to
От | Bruce Momjian |
---|---|
Тема | Re: BUG #2195: log_min_messages crash server when in DEBUG3 to |
Дата | |
Msg-id | 200601261855.k0QItHN13307@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #2195: log_min_messages crash server when in DEBUG3 to (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #2195: log_min_messages crash server when in DEBUG3 to
(Tom Lane <tgl@sss.pgh.pa.us>)
|
Список | pgsql-bugs |
Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > Tom Lane wrote: > >> I tried on CVS tip and don't see a problem. Which branch were you > >> testing? > > > Uh, CVS HEAD. I put -DEXEC_BACKEND into Makefile.custom, and recompiled > > and initdb'ed. I then modified postgresql.conf and set log_min_messages > > to "debug5". Then stop and start the server. The server log looks like > > the server is running, but you cannot connect using psql, so something > > died. > > [ scratches head... ] I put "#define EXEC_BACKEND 1" into pg_config.h > instead, and didn't bother to initdb, but otherwise the same. Wonder > why it's not failing for me. Something platform-specific maybe? I just tested again using your pg_config.h modification, and I still get the failure, so perhaps BSD/OS and Win32 have similar issues with our code. Trimming off the environment output, attached is the log file with the sig11/segfault failure. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 DEBUG: invoking IpcMemoryCreate(size=37224448) DEBUG: max_safe_fds = 112, usable_fds = 122, already_open = 6 LOG: database system was shut down at 2006-01-26 13:52:54 EST LOG: checkpoint record is at 0/3444F8 LOG: redo record is at 0/3444F8; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 570; next OID: 16385 LOG: next MultiXactId: 1; next MultiXactOffset: 0 LOG: database system is ready LOG: transaction ID wrap limit is 2147484146, limited by database "postgres" DEBUG: proc_exit(0) DEBUG: shmem_exit(0) DEBUG: exit(0) DEBUG: forked new backend, pid=13011 socket=7 DEBUG: server process (PID 13011) was terminated by signal 11 LOG: server process (PID 13011) was terminated by signal 11 LOG: terminating any other active server processes DEBUG: sending SIGQUIT to process 12978 DEBUG: sending SIGQUIT to process 12979 DEBUG: proc_exit(0) DEBUG: shmem_exit(0) DEBUG: exit(0) LOG: all server processes terminated; reinitializing DEBUG: shmem_exit(0) DEBUG: invoking IpcMemoryCreate(size=37224448) LOG: database system was interrupted at 2006-01-26 13:52:55 EST LOG: checkpoint record is at 0/3444F8 LOG: redo record is at 0/3444F8; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 570; next OID: 16385 LOG: next MultiXactId: 1; next MultiXactOffset: 0 LOG: database system was not properly shut down; automatic recovery in progress LOG: record with zero length at 0/34453C LOG: redo is not required LOG: database system is ready LOG: transaction ID wrap limit is 2147484146, limited by database "postgres" DEBUG: proc_exit(0) DEBUG: shmem_exit(0) DEBUG: exit(0)
В списке pgsql-bugs по дате отправления:
Предыдущее
От: Tom LaneДата:
Сообщение: Re: BUG #2195: log_min_messages crash server when in DEBUG3 to
Следующее
От: Tom LaneДата:
Сообщение: Re: BUG #2195: log_min_messages crash server when in DEBUG3 to