Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBKF9Wm22584 for ; Thu, 20 Dec 2001 10:09:32 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fBKF9Wi08402; Thu, 20 Dec 2001 10:09:32 -0500 (EST) To: "Robert B. Easter" cc: "Peter T. Brown" , pgsql-sql@postgresql.org Subject: Re: controlling process priority In-reply-to: <200112201324.fBKDOgM15049@comptechnews.com> References: <007301c18902$39df9b20$7d00000a@PETER> <200112201324.fBKDOgM15049@comptechnews.com> Comments: In-reply-to "Robert B. Easter" message dated "Thu, 20 Dec 2001 08:24:41 -0500" Date: Thu, 20 Dec 2001 10:09:32 -0500 Message-ID: <8399.1008860972@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200112/218 X-Sequence-Number: 6040 "Robert B. Easter" writes: > [ C function to nice down the backend ] This sort of thing has been suggested before, but I've always wondered whether it isn't counterproductive. The trouble is priority inversion: any time the niced backend is holding a lock on some shared datastructure, it will be blocking the allegedly-higher-priority other backends. regards, tom lane