=?ISO-8859-1?Q?Christian_Schr=F6der?= <cs@xxxxxxxxx> writes: > [ ongoing saga ] I don't think you ever mentioned exactly what platform you're running on; it seems to be some 64-bit Linux variant but you didn't say which. I've been futilely trying to reproduce the hang on a Xeon Fedora Core 6 machine, and just now I noticed what might be a significant discrepancy. You showed this in a gdb printout: > Reading symbols from > /usr/lib/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so...done. > Loaded symbols for > /usr/lib/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so > Reading symbols from /lib64/libpthread.so.0...done. > [Thread debugging using libthread_db enabled] > [New Thread 47248855881456 (LWP 7129)] > Loaded symbols for /lib64/libpthread.so.0 > Reading symbols from > /usr/lib/perl5/5.8.8/x86_64-linux-thread-multi/auto/Opcode/Opcode.so...done. > Loaded symbols for > /usr/lib/perl5/5.8.8/x86_64-linux-thread-multi/auto/Opcode/Opcode.so On my machine the corresponding lines point to /usr/lib64: Reading symbols from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so...done. Loaded symbols for /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so Reading symbols from /lib64/libpthread.so.0...done. [Thread debugging using libthread_db enabled] [New Thread 46912496247568 (LWP 344)] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/auto/Opcode/Opcode.so...done. Loaded symbols for /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/auto/Opcode/Opcode.so Maybe this is just a cross-distribution difference in file layouts, but I'm suddenly wondering if there's a 32-vs-64-bit issue here. Exactly which perl packages have you got installed? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org/