Re: Problem on AIX with current

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: ZeugswetterA(at)spardat(dot)at, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Problem on AIX with current
Date: 2001-10-04 04:07:17
Message-ID: 20011004130717J.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2001-10-04 04:08:22 Re: [HACKERS] int4eq (xid, int4)
Previous Message Tom Lane 2001-10-04 03:49:49 Re: Unicode combining characters