From: Yann-Ju Chu <yjchui@ms.chttl.com.tw>
To: pgsql-sql@postgresql.org, "Ãhô" <marslin@ms.chttl.com.tw>
To: ³¯ÀA¬w <jjchen@ms.chttl.com.tw>
To: ªL®Ê±X <jl0@ms.chttl.com.tw>
Subject: stuck spinlock in postgresql-6.5.1
Date: Fri, 30 Jul 1999 10:17:44 +0800
Message-ID: <37A10B48.4A47F6AA@ms.chttl.com.tw> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: yjchui@ms.chttl.com.tw, marslin@ms.chttl.com.tw, jjchen@ms.chttl.com.tw, jl0@ms.chttl.com.tw
Subject: Re: stuck spinlock in postgresql-6.5.1
In-Reply-To: <37A10B48.4A47F6AA@ms.chttl.com.tw>
References: <37A10B48.4A47F6AA@ms.chttl.com.tw>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox