> If you have no better way of determining what's going on, it might help > to recompile with LOCK_DEBUG defined, then enable trace_lwlocks in > postgresql.conf (better turn on debug_print_query, log_timestamp, and > log_pid too). This will generate rather voluminous log output, perhaps > enough to provide a clue.
When I recompiled with LOCK_DEBUG and trace_lwlocks = true, it *works* (and saw lots of lock debugging messages, of course). However if I turn trace_lwlocks to off, the backend stucks again. Is there anything I can do? Note the machine has 4 processors. Is that related to? -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
