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 2CB77D1B51B for ; Fri, 24 Oct 2003 20:51:05 +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 67453-08 for ; Fri, 24 Oct 2003 17:50:36 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 4C962D1B52B for ; Fri, 24 Oct 2003 17:50:33 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h9OKoYX22829; Fri, 24 Oct 2003 16:50:34 -0400 (EDT) From: Bruce Momjian Message-Id: <200310242050.h9OKoYX22829@candle.pha.pa.us> Subject: Re: My own performance/tuning q&a In-Reply-To: <16281.22423.26659.54130@yertle.int.kciLink.com> To: Vivek Khera Date: Fri, 24 Oct 2003 16:50:34 -0400 (EDT) Cc: pgsql-performance@postgresql.org X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/633 X-Sequence-Number: 4381 Vivek Khera wrote: > >>>>> "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. Yes, I think Tom's concern was priority inversion, where a low priority process holds a lock while a higher one waits for it. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073