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 1jxZXw-0001zu-1h for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Jul 2020 17:25:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jxZXu-0008Rg-NP for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Jul 2020 17:25:46 +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 1jxZXu-0008RY-C7 for pgsql-hackers@lists.postgresql.org; Mon, 20 Jul 2020 17:25:46 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jxZXs-0002Xh-1s for pgsql-hackers@postgresql.org; Mon, 20 Jul 2020 17:25:45 +0000 Received: by mail-ej1-x62e.google.com with SMTP id n22so15983043ejy.3 for ; Mon, 20 Jul 2020 10:25:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ZlLWa8GEHw1SCJhsZQxDhwD6Iqrvd06G3oKz17k02tY=; b=mGT+9MsyYZ2cRCsPiUmh+79ETbeqtYSjH4UAL78mpJIADL6ZSqDN0Bskjz8oul2xgc 0h43Bf0TbZ6WxSvbCtlLcTIrejrGCZvy8ooqgV3BkQbV5vWvZ5KVABtTCk2juuPTLjsH uBrLM4/z3JlG+KkLO9zQHq1r0YeOFjrBAbBMagA3yHrcIVfi/rlhQ652lRP7B0mv/gb8 mQLQvGWbEKD03N6komFGVNgF3Y7kGjZl/vYqxF9vJkFYLLBpmDjYaRDHKn5wfsXoUS/Q BkJOuRNniP9rHow7Kmn1QuAVkLR81HvpcmElAqMf6lHtJ7P7u4JhUcNCfkR22y5q9S0+ /ezA== 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; bh=ZlLWa8GEHw1SCJhsZQxDhwD6Iqrvd06G3oKz17k02tY=; b=FLwbAv4UrzhGuASumIUVxnndoeMrPorB1N/mVeJjri3CJaYh/+1KgCOKVdaiv/T3WJ skcXBaiwr0iqwTQZtjSQlm+Qiinazjx0ofI5jqw6FyTY1uiR2H8mWqG/63+B11YObgud PnGqODlMW3V6Bq2HNJslXEZ+WkyT+kv4bepizpgmoHN4nS2wQnM2w2/OQXzH+3CpzpfJ /PwKJ6HXLdGAF8mFz7omm7e8TRoJrQTO/jyiombg9mLNO81uAdKiTu1xuk1PKDIGner0 m1/kR1y0YJ6d1jFk+tFA27OaPWxd1hyl6BBYTyK7ftm2uthtXfjPYY2syEBZ8W0LXCKx 7+GA== X-Gm-Message-State: AOAM533XtvET5jQ8tRQb/Un0U7WX0sJ11Z0GDnwZIPFNCC2fqtFYNfmR aTxtls5/wQziwcLNdcfM5QrCiw== X-Google-Smtp-Source: ABdhPJx8xTKtEl3YPBBwiPmxPSz67VzGsU9evhtnTvHAMADEqOb3XKAN/SvGHBHxW4tyWOkVNi3xww== X-Received: by 2002:a17:906:ca43:: with SMTP id jx3mr21118315ejb.208.1595265941768; Mon, 20 Jul 2020 10:25:41 -0700 (PDT) Received: from localhost (ip-86-49-253-141.net.upcbroadband.cz. [86.49.253.141]) by smtp.gmail.com with ESMTPSA id u13sm15498881eds.10.2020.07.20.10.25.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Jul 2020 10:25:40 -0700 (PDT) Date: Mon, 20 Jul 2020 19:25:39 +0200 From: Tomas Vondra To: Tom Lane Cc: Jeff Davis , Peter Geoghegan , Alvaro Herrera , David Rowley , Stephen Frost , Andres Freund , Bruce Momjian , Robert Haas , Justin Pryzby , Melanie Plageman , "pgsql-hackers@postgresql.org" Subject: Re: Default setting for enable_hashagg_disk Message-ID: <20200720172539.6jov6ynljly4wj6i@development> References: <9e4a4cffe3eee0543e5b94c90821d39e03b81d29.camel@j-davis.com> <6d0aba397625df79bdc3ca85adc11b9e48ecb0da.camel@j-davis.com> <4118680.1595097043@sss.pgh.pa.us> <571473265c5d5309f4012855ebd2131c136073ab.camel@j-davis.com> <32871.1595121333@sss.pgh.pa.us> <88c0af01ad9ac105e424768808a214d855e29a77.camel@j-davis.com> <20200720004827.4c46ikcdrfum6xyu@development> <400617.1595251041@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <400617.1595251041@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Jul 20, 2020 at 09:17:21AM -0400, Tom Lane wrote: >Tomas Vondra writes: >> There's a minor problem here, though - these stats were collected before >> we fixed the tlist issue, so hashagg was spilling about 10x the amount >> of data compared to sort+groupagg. So maybe that's the first thing we >> should do, before contemplating changes to the costing - collecting >> fresh data. I can do that, if needed. > >+1. I'm not sure if we still need to do anything, but we definitely >can't tell on the basis of data that doesn't reliably reflect what >the code does now. > OK, will do. The hardware is busy doing something else at the moment, but I'll do the tests and report results in a couple days. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services