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 A5925D1B527 for ; Fri, 24 Oct 2003 16:47:50 +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 28231-01 for ; Fri, 24 Oct 2003 13:47:19 -0300 (ADT) Received: from yertle.kcilink.com (yertle.kcilink.com [216.194.193.105]) by svr1.postgresql.org (Postfix) with ESMTP id D5E0FD1B50C for ; Fri, 24 Oct 2003 13:47:18 -0300 (ADT) Received: by yertle.kcilink.com (Postfix, from userid 100) id 20F9A2178A; Fri, 24 Oct 2003 12:47:19 -0400 (EDT) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16281.22423.26659.54130@yertle.int.kciLink.com> Date: Fri, 24 Oct 2003 12:47:19 -0400 To: pgsql-performance@postgresql.org Subject: Re: My own performance/tuning q&a In-Reply-To: References: X-Mailer: VM 7.14 under 21.4 (patch 12) "Portable Code" XEmacs Lucid X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/621 X-Sequence-Number: 4369 >>>>> "sm" == scott marlowe writes: sm> Note that Tom has mentioned problems with possible deadlocks when nicing sm> individual backends before, so proceed with caution here. I can see possible starvation, but if scheduling changes cause deadlocks, then there's something wrong with the design. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/