Received: from firewall.chttl.com.tw (gate.chttl.com.tw [202.39.157.254]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA54582 for ; Thu, 29 Jul 1999 22:19:11 -0400 (EDT) (envelope-from yjchui@ms.chttl.com.tw) Received: from chttl.com.tw (ms.tl.gov.tw. [10.144.2.104]) by firewall.chttl.com.tw (8.9.3/8.9.3) with ESMTP id KAA26241 for ; Fri, 30 Jul 1999 10:19:09 +0800 (CST) Received: from ms.chttl.com.tw ([10.144.169.38]) by chttl.com.tw (8.9.3/8.9.3) with ESMTP id KAA11095; Fri, 30 Jul 1999 10:17:59 +0800 (CST) Message-ID: <37A10B48.4A47F6AA@ms.chttl.com.tw> Date: Fri, 30 Jul 1999 10:17:44 +0800 From: Yann-Ju Chu X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org, "=?iso-8859-1?Q?=C3h=AD=F4?=" , "=?iso-8859-1?Q?=B3=AF=C0A=ACw?=" , "=?iso-8859-1?Q?=AAL=AE=CA=B1X?=" Subject: stuck spinlock in postgresql-6.5.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have updated my DB from postgresql-6.4.2 to version 6.5.1 to slove the stuck spinlock problems. But it seems not work. I have both large of data to be updated to DB "all the time" but also have large amount of proccessess to access (update) the database simultaneously. If the number of processes is below 6, everything work fine. However, when the number of processes accessing the database increases, then, stuck spinlock happens soon after all the processes start. Because the accessed rows by these processes is mutual exclusive, I do not have any "LOCK table" or "SELECT FOR UPDATE" command in all the process. I have updated the postgresql to 6.5.1 but stuck spinlock happens. Does anybody know that whether the problem is caused by database, or by the database application written by me? Thanks Y.J. Chu