Re: Problem on AIX with current

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

Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> 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.

Ugh ... ye classic Heisenbug ...

> Is there anything I can do?

Apparently the problem is timing-sensitive, which is hardly surprising
for a lock issue. You might find that it occurs some of the time if
you repeat the test over and over.

> Note the machine has 4 processors. Is that related to?

Hard to tell at this point, but considering that no one else has
reported a problem so far, it does seem like multiple CPUs at least
help to make the failure more probable. But it could just be a
portability problem. Do you have another machine with identical OS
and fewer processors to try for comparison?

Andreas, have you tried CVS tip lately on AIX? What's your results?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-10-04 04:30:13 Re: Unicode combining characters
Previous Message Tatsuo Ishii 2001-10-04 04:11:21 Re: Unicode combining characters