X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C89D7D1B4C8 for ; Thu, 18 Dec 2003 20:31:20 +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 77069-06 for ; Thu, 18 Dec 2003 16:30:33 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id EEDF2D1B53E for ; Thu, 18 Dec 2003 16:30:31 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id hBIKUVU6044642 for ; Thu, 18 Dec 2003 20:30:31 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id hBIKA0IS019960 for pgsql-performance@postgresql.org; Thu, 18 Dec 2003 20:10:00 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: why do optimizer parameters have to be set manually? Date: Thu, 18 Dec 2003 14:17:43 -0500 Organization: Hub.Org Networking Services Lines: 23 Message-ID: <60n09q9bqg.fsf@dev6.int.libertyrms.info> References: <3FE1F5A1.6080908@geizhals.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Reasonable Discussion, linux) Cancel-Lock: sha1:986zF5HVCKX8G4/7FrcwSG24Oek= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/266 X-Sequence-Number: 5126 mjy@geizhals.at ("Marinos J. Yannikos") writes: > it seems to me that the optimizer parameters (like random_page_cost > etc.) could easily be calculated and adjusted dynamically be the DB > backend based on the planner's cost estimates and actual run times for > different queries. Perhaps the developers could comment on that? Yes, it seems like a Small Matter Of Programming. http://wombat.doc.ic.ac.uk/foldoc/foldoc.cgi?SMOP In seriousness, yes, it would seem a reasonable idea to calculate some of these values a bit more dynamically. I would be inclined to start with something that ran a workload, and provided static values based on how that workload went. That would require NO intervention inside the DB server; it could be accomplished simply by writing a database script. Feel free to contribute either a script or a backend "hack"... -- let name="cbbrowne" and tld="libertyrms.info" in String.concat "@" [name;tld];; Christopher Browne (416) 646 3304 x124 (land)