Milen A. Radev wrote:
I was able to reproduce this on Unix by adding -DEXEC_BACKEND to the
compile line. It errors out on DEBUG3 and higher. I assume the problem
is that the debug system is not initialized properly in the EXEC_BACKEND
case. Win32 uses -DEXEC_BACKEND so that is why Win32 is failing.

--
Bruce Momjian | http://candle.pha.pa.us
pgman (AT) candle (DOT) 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

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Bruce Momjian <pgman (AT) candle (DOT) pha.pa.us> writes:
I tried on CVS tip and don't see a problem. Which branch were you
testing?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Tom Lane wrote:
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.

--
Bruce Momjian | http://candle.pha.pa.us
pgman (AT) candle (DOT) 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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Bruce Momjian <pgman (AT) candle (DOT) pha.pa.us> writes:
[ 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?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

--ELM1138301717-10037-0_
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Tom Lane wrote:
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 (AT) candle (DOT) 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

--ELM1138301717-10037-0_
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
Content-Disposition: inline; filename="/rtmp/log"

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)

--ELM1138301717-10037-0_
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

--ELM1138301717-10037-0_--

Bruce Momjian <pgman (AT) candle (DOT) pha.pa.us> writes:
Hmph. I've just been trying to reproduce it on Linux (FC4), and it's
OK for me there as well as on HPUX where I tried first. Odder and
odder.

Oh, if you're getting a segfault, could we see the backtrace?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

I wrote:
Actually, maybe the failure requires some configure option I'm not using
.... what's your configure command?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Tom Lane wrote:
configure \
--with-x \
--with-tcl \
--with-perl \
--enable-pltcl-unknown \
--with-tclconfig=/u/lib \
--with-tkconfig=/u/lib \
--with-includes="/usr/local/include/readline /usr/contrib/include" \
--with-libraries="/usr/local/lib /usr/contrib/lib" \
--enable-locale \
--enable-multibyte \
--with-openssl \
--enable-cassert \
--enable-thread-safety \
--enable-nls

--
Bruce Momjian | http://candle.pha.pa.us
pgman (AT) candle (DOT) 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

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Bruce Momjian <pgman (AT) candle (DOT) pha.pa.us> writes:
Still can't reproduce it here. What stack trace do you get from the
crash?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend