X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 0EC33475F16 for ; Fri, 2 May 2003 10:23:08 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 416D4475C3D for ; Fri, 2 May 2003 10:23:07 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h42ENAU6010242; Fri, 2 May 2003 10:23:10 -0400 (EDT) To: Peter Childs Cc: pgsql-performance@postgresql.org Subject: Re: Query Priority In-reply-to: References: Comments: In-reply-to Peter Childs message dated "Fri, 02 May 2003 13:55:01 +0100" Date: Fri, 02 May 2003 10:23:10 -0400 Message-ID: <10241.1051885390@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-32.3 required=5.0 tests=BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200305/6 X-Sequence-Number: 1785 Peter Childs writes: > Is there some way to give some postgres backends higher priority. No. > I don't think this would be too difficult to do as certainly on > Linux the process could just be reniced and the os left to figure it out. Read about "priority inversion" in any handy CS textbook ... renicing a process won't buy you much if the locking mechanisms don't cooperate. regards, tom lane