X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 38449D1CA77 for ; Tue, 13 Apr 2004 15:46:06 -0300 (ADT) 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 40858-03 for ; Tue, 13 Apr 2004 15:46:01 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E66F1D1C9C4 for ; Tue, 13 Apr 2004 15:45:58 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i3DIjvD4025220; Tue, 13 Apr 2004 14:45:57 -0400 (EDT) To: Nichlas =?iso-8859-1?Q?L=F6fdahl?= Cc: pgsql-admin@postgresql.org Subject: Re: log_min_cost_statement In-reply-to: <20040413152601.GA22288@shaka.acc.umu.se> References: <20040413152601.GA22288@shaka.acc.umu.se> Comments: In-reply-to Nichlas =?iso-8859-1?Q?L=F6fdahl?= message dated "Tue, 13 Apr 2004 17:26:01 +0200" Date: Tue, 13 Apr 2004 14:45:57 -0400 Message-ID: <25219.1081881957@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/205 X-Sequence-Number: 13178 Nichlas =?iso-8859-1?Q?L=F6fdahl?= writes: > Would it be possible to have an option "log_min_cost_statement", similar to > "log_min_duration_statement" except that it logs all statement that has > an minimum cost estimated by the planner? I think it would be easier to > find unoptimized queries that way. Why would you want to filter on the planner's cost estimate rather than the true runtime? regards, tom lane