X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8460ED1D0B8 for ; Thu, 19 Feb 2004 09:26:22 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 62521-10 for ; Thu, 19 Feb 2004 05:26:28 -0400 (AST) Received: from frodo.hserus.net (frodo.hserus.net [204.74.68.40]) by svr1.postgresql.org (Postfix) with ESMTP id A2E42D1CB1D for ; Thu, 19 Feb 2004 05:26:20 -0400 (AST) Received: from concord.pspl.co.in ([202.54.11.72]:63314 helo=ps0499.intranet.pspl.co.in) by frodo.hserus.net with asmtp (Cipher TLSv1:RC4-MD5:128) (Exim 4.30 #0) id 1AtkRt-0008oc-AT by authid with plain; Thu, 19 Feb 2004 14:56:25 +0530 From: Shridhar Daithankar Reply-To: shridhar@frodo.hserus.net To: "Saleem Burhani Baloch" Subject: Re: Slow response of PostgreSQL Date: Thu, 19 Feb 2004 14:56:19 +0530 User-Agent: KMail/1.6 References: <200402190901.i1J91KY07596@ns2.khi.wol.net.pk> In-Reply-To: <200402190901.i1J91KY07596@ns2.khi.wol.net.pk> Cc: pgsql-performance@postgresql.org MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402191456.19032.shridhar@frodo.hserus.net> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/222 X-Sequence-Number: 5746 On Thursday 19 February 2004 14:31, Saleem Burhani Baloch wrote: > Hi, > > Thanks every one for helping me. I have upgraded to 7.4.1 on redhat 8 ( rh > 9 require a lot of lib's) and set the configuration sent by Chris. Now the > query results in 6.3 sec waooo. I m thinking that why the 7.1 process > aggregate slowly. Anyway. > > I still have to go for 2 sec result and now I m thinking to go for Free BSD > 5.2. Before that you can try something with kernel 2.6.3. I think it could make the difference you are looking at. > The record locking by "select ..... update for" is working fine, but a > situation arrises when the second user goes for locking the record, the > task will wait untill the first user ends up his work. IS their is a way > that we can know or get a message that the row/record is already locked by > some one else. Right now, it is hotly debated on HACKERS about adding a NOWAIT clause to SELECT FOR UPDATE. If you think your application deployment is away for months and can try CVS head, you can expect some action on it in coming few days. As a side bonus you would be benefitted by performance and scalability additions that won't make there way in 7.4 stream. HTH Shridhar