Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XrgW0-0007NC-IH for pgsql-performance@arkaria.postgresql.org; Fri, 21 Nov 2014 05:12:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XrgW0-0001sT-2M for pgsql-performance@arkaria.postgresql.org; Fri, 21 Nov 2014 05:12:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XrgVy-0001qY-P7 for pgsql-performance@postgresql.org; Fri, 21 Nov 2014 05:12:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XrgVr-0000hM-6x for pgsql-performance@postgresql.org; Fri, 21 Nov 2014 05:12:13 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id sAL5C5GR021115; Fri, 21 Nov 2014 00:12:05 -0500 From: Tom Lane To: Stuart Bishop cc: "pgsql-performance@postgresql.org" Subject: Re: A pessimistic planner In-reply-to: References: Comments: In-reply-to Stuart Bishop message dated "Fri, 21 Nov 2014 12:07:27 +0700" Date: Fri, 21 Nov 2014 00:12:05 -0500 Message-ID: <21114.1416546725@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Stuart Bishop writes: > I was wondering if the planner should be much more pessimistic, > trusting in Murphy's Law and assuming the worst case is the likely > case? Would this give me a much more consistent system? Well, it would give uniformly awful plans for cases where fast-start plans are actually useful ... and there are plenty. We do need to think of ways to account for risk, but I don't think that jamming the tiller all the way over is likely to be a net improvement. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance