Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jjZhW-0002wS-Fy for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Jun 2020 02:45:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jjZhU-0007bY-VO for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Jun 2020 02:45:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jjZhU-0007bQ-Od for pgsql-hackers@lists.postgresql.org; Fri, 12 Jun 2020 02:45:48 +0000 Received: from mail-il1-x12b.google.com ([2607:f8b0:4864:20::12b]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jjZhS-0001Fy-1K for pgsql-hackers@postgresql.org; Fri, 12 Jun 2020 02:45:47 +0000 Received: by mail-il1-x12b.google.com with SMTP id z2so7512357ilq.0 for ; Thu, 11 Jun 2020 19:45:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=KGS0sRZk6QidLdXIQocCOLavlZlSZ26g+Bw1TnMqhyc=; b=Hstf3XkTuT95ipDmBxg+7vcLvDWC4XwTEAN4NddzlgCZpKZLcKtkaCISYXx3l/jtpF T9Fb+ZTOx78p+HVd6f2ltIlF/eGm0+724YhBHWGxIznqz0CtPYoq/iPoCQAU3Qf/LYlC TdsZYvGhOqUf85YVxd3nALjZvspwCZg4kkLyiSufNDHy4XrDfXB/s7Nx+ugBPQ6mrhh8 5ebMiIDwO+kTu6Ml9OQpqLzbmxdU0KSKCypN0ErkVFUP3ZqRGa2B7n7OKXL9h/v0tVWB 57Mv2it4g3XDvBLuR2GqXErb6knNPMCdZmiInjmff6jzvkJcm+hQXu/6yh2jBy7XIB86 Nh8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=KGS0sRZk6QidLdXIQocCOLavlZlSZ26g+Bw1TnMqhyc=; b=WmIgG1kdlGHboVidJFBGoeP8+4s7awpzDk73XKudS4m5c74sGTQ6bjNgTmlfs9Yh1l EoBvJCTW93Gp1DaTDowdiigcCpm3bIX5xs22ASQvn/f6VbnFWZ4BpO/IXM0Yl92O6mIO Ui0DI+zJnimOfh8xkfAZMQVdVj822GXxYQRym6w9SL5BaxAY+9SNi98Vx+9lnT2zSaXy JPtBg8FQhsM/1wcresYWOyckbd6sh+Y/XqqonAaV2OzVggbziG42MDBBJzcXHQHYyl5s MnNB5F0K+Pr6NZCHKthiPRE56FQYSp7pN/sZyQ+dME7WWV7KFkbG4w7Lrc8xZTXsEerc ypjQ== X-Gm-Message-State: AOAM533o3XXIOMstsCmFm+RWCExUeJSMKMAILqcaoYnHS4hOPuT6TCp5 QnL+yL+fyV5Ryr0a67Zgc9dLhQ== X-Google-Smtp-Source: ABdhPJyuCfh7bOA8Zs/eCX+XqduCbIj3YqUdPOmY5HTeN/ydS+mIEKGIjP3UKW96TY3un7zbP70vZA== X-Received: by 2002:a92:a1c9:: with SMTP id b70mr11272539ill.198.1591929945159; Thu, 11 Jun 2020 19:45:45 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id r20sm2585472ilk.44.2020.06.11.19.45.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jun 2020 19:45:44 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 21EBE8001A5; Thu, 11 Jun 2020 21:45:43 -0500 (CDT) Date: Thu, 11 Jun 2020 21:45:43 -0500 From: Justin Pryzby To: Jeff Davis Cc: Melanie Plageman , Robert Haas , Tomas Vondra , pgsql-hackers@postgresql.org Subject: Re: Default setting for enable_hashagg_disk Message-ID: <20200612024542.GD14879@telsasoft.com> References: <9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com> <20200407223900.GT2228@telsasoft.com> <20200409114855.h4hh7e2wt77p56sv@development> <6292f5a766198d5745eb8cc17ac736366056671d.camel@j-davis.com> <20200610021544.GA14879@telsasoft.com> <8bff2e4e8020c3caa16b61a46918d21b573eaf78.camel@j-davis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Jun 11, 2020 at 01:22:57PM -0700, Jeff Davis wrote: > On Wed, 2020-06-10 at 11:39 -0700, Jeff Davis wrote: > > 1. Testing the spilling of hashed grouping sets: I'm inclined to just > > get rid of enable_groupingsets_hash_disk and use Melanie's stats- > > hacking approach instead. > > Fixed in 92c58fd9. > > > think the names you suggested quite fit, but the idea to use a more > > interesting GUC value might help express the behavior. Perhaps making > > enable_hashagg a ternary "enable_hashagg=on|off|avoid_disk"? The word > > "reject" is too definite for the planner, which is working with > > imperfect information. > > I renamed enable_hashagg_disk to hashagg_avoid_disk_plan, which I think > satisfies the concerns raised here. Also in 92c58fd9. Thanks for considering :) I saw you updated the Open Items page, but put the items into "Older Bugs / Fixed". I moved them underneath "Resolved" since they're all new in v13. https://wiki.postgresql.org/index.php?title=PostgreSQL_13_Open_Items&diff=34995&oldid=34994 -- Justin