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 543A8D1E0CD for ; Fri, 20 Feb 2004 14:34:35 +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 93247-04 for ; Fri, 20 Feb 2004 10:34:34 -0400 (AST) Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by svr1.postgresql.org (Postfix) with ESMTP id AF52DD1DA34 for ; Fri, 20 Feb 2004 10:34:30 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by bob.samurai.com (Postfix) with ESMTP id 490E81EC7; Fri, 20 Feb 2004 09:34:34 -0500 (EST) Received: from bob.samurai.com ([127.0.0.1]) by localhost (bob.samurai.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 37935-01-7; Fri, 20 Feb 2004 09:34:33 -0500 (EST) Received: from tokyo.samurai.com (d226-89-59.home.cgocable.net [24.226.89.59]) by bob.samurai.com (Postfix) with ESMTP id 7DC301E96; Fri, 20 Feb 2004 09:34:32 -0500 (EST) To: shridhar@frodo.hserus.net Cc: "Saleem Burhani Baloch" , pgsql-performance@postgresql.org Subject: Re: Slow response of PostgreSQL From: Neil Conway In-Reply-To: <200402191456.19032.shridhar@frodo.hserus.net> (Shridhar Daithankar's message of "Thu, 19 Feb 2004 14:56:19 +0530") References: <200402190901.i1J91KY07596@ns2.khi.wol.net.pk> <200402191456.19032.shridhar@frodo.hserus.net> Date: Fri, 20 Feb 2004 09:34:31 -0500 Message-ID: <87d689es5k.fsf@mailbox.samurai.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at mailbox.samurai.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/234 X-Sequence-Number: 5758 Shridhar Daithankar writes: > 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. You can also try using the statement_timeout configuration variable that is already included with 7.4. It's not exactly "don't wait for locks", but should approximate that behavior well enough. http://www.postgresql.org/docs/7.4/static/runtime-config.html#RUNTIME-CONFIG-CLIENT -Neil