Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E2BF29FC4FE for ; Fri, 23 Feb 2007 18:38:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 23723-09 for ; Fri, 23 Feb 2007 18:38:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id C36FD9FC4EC for ; Fri, 23 Feb 2007 18:38:29 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id EF39F56491; Fri, 23 Feb 2007 16:38:28 -0600 (CST) Received: (hashcash-sendmail, from uid 1001); Fri, 23 Feb 2007 16:38:27 -0600 Date: Fri, 23 Feb 2007 16:38:27 -0600 From: "Jim C. Nasby" To: Ron Mayer , pgsql-general@postgresql.org Subject: Re: Priorities for users or queries? Message-ID: <20070223223826.GC11743@decibel.org> References: <45D65E08.7000306@cheapcomplexdevices.com> <200702170152.l1H1qax16645@momjian.us> <45DB81EA.9080401@cheapcomplexdevices.com> <45DF499C.4090305@cheapcomplexdevices.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45DF499C.4090305@cheapcomplexdevices.com> X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070223:rm_pg@cheapcomplexdevices.com::plaxfe+HerMRoIj5:00000000 000000000000000000000000661z X-Hashcash: 1:20:070223:pgsql-general@postgresql.org::i/gYclHGYfe7QV8k:000000000 0000000000000000000000005Z+p X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/1413 X-Sequence-Number: 109902 On Fri, Feb 23, 2007 at 12:07:56PM -0800, Ron Mayer wrote: > Jim Nasby wrote: > > The problem with using simple OS priority settings is you leave yourself > > wide open to priority inversion. > > Which is why you either > (a) note that papers studying priority inversion on RDBMS's > find that it's a non issue on many RDBMS workloads; and > (except for real-time databases) you tend to still get > at least partial benefits even in the face of priority > inversions. > or > (b) use a scheduler in your OS that supports priority > inheritance or other mechanisms to avoid priority > inversion problems. > If you want to use priority inheritance to avoid > the priority inversion settings it appears versions > of Linux, BSD, Windows, and Solaris at least give > you the ability to do so. > > > There is already work being done on a queuing system; take a look at the > > bizgres archives. > > Which is cool; but not quite the same as priorities. > > It seems to me that Bizgres and/or PostgreSQL would not > want to re-implement OS features like schedulers. Actually, I believe part of the discussion also involved how to handle long-running workloads that you don't want to monopolize the machine. -- Jim C. Nasby, Database Architect decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"