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 1jsfkl-0004PM-Pn for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Jul 2020 05:02:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jsfkk-00036l-Hf for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Jul 2020 05:02: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 1jsfkk-00036c-6z for pgsql-hackers@lists.postgresql.org; Tue, 07 Jul 2020 05:02:46 +0000 Received: from mail-io1-xd43.google.com ([2607:f8b0:4864:20::d43]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jsfkh-00061I-AI for pgsql-hackers@postgresql.org; Tue, 07 Jul 2020 05:02:44 +0000 Received: by mail-io1-xd43.google.com with SMTP id i4so41746523iov.11 for ; Mon, 06 Jul 2020 22:02:42 -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=oLTAniKvKI9CkGtwOq8NCdmS6HOsnElMfwVSM6XSUdU=; b=jVrdmGeMe6YX9PDJP/IMiTdLEt61uBVDdCbxZEUWpSaeMMDxOAhbv2qkkT5UgxjFe8 IXd7yFceRm+6usKccMyzfwU0DpFXSXVBR+IaFRTYdage2eIWD+/iIEo7dyU14Uw2aeEl ehNueEnXO68ZCXJF/wdYhnuqQ8OYVFWdPqmDoOwk+GaJi3CyxSaVzbbMdOX2THROWSEJ DsmgEW1lXdkeO3Gw3+r5QniCDAdlfn71bhodGisTBWs1TiXh0VCwXcejPUOQoQL1+TAq OH9va2TVp56o+cMy2sB21FRsPst49AJhbc8P7N0KzgWv1jSSj6A14xbSU9LJREHLEMHr 4VFw== 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=oLTAniKvKI9CkGtwOq8NCdmS6HOsnElMfwVSM6XSUdU=; b=GpR4x5EWU6AP6Hwt90AyrmWOdzQTv3/9/5SESI2/Qp/BR4UCOWusPftILOhS5X6QY3 63wOZkBonk+u7L1rRNc5dI4vBHJxHVr2mi6W89i3Z2oIcryI49Csjk5cX2F0LpFAgLGJ dip0/woSi/OF9vgMcAaezsSzxmsr5ObfRrN2ZG0bQmsMOD1tf8GMLqEtXS/dlmhyVGwb 92ljVRQ7k7tS1ZU+NM7G3TGXj41MYmoWRCZiE4SWLO7vdSexKhZnyOtXENoOtBTLS53B BqUJt3HqqPz/K7bfRUQxZOuyQ+Sq0LD3ylieoCxlXfwjvxObr3dQnClsRrVuMEx0SnrL LKbQ== X-Gm-Message-State: AOAM530N30KG1UIw6FPdmo4xb/suFI7ZfLD6+S7Oqd+J5nFV+hTIm6Jd JDZuwGKSHTBDDF9BA1MXBCIWrQ== X-Google-Smtp-Source: ABdhPJymAnZ27+n22L/cb/wo2Ud/PI5a+/M1EWf0iCFfQSa4fQWLA8Gz40snaETxczzPwVjPTeSfCg== X-Received: by 2002:a6b:9042:: with SMTP id s63mr29744670iod.195.1594098161762; Mon, 06 Jul 2020 22:02:41 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id 186sm8394421iow.26.2020.07.06.22.02.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Jul 2020 22:02:40 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 83C81800878; Tue, 7 Jul 2020 00:02:39 -0500 (CDT) Date: Tue, 7 Jul 2020 00:02:39 -0500 From: Justin Pryzby To: Jeff Davis Cc: Peter Geoghegan , Amit Kapila , Bruce Momjian , Tomas Vondra , Robert Haas , Andres Freund , David Rowley , Melanie Plageman , pgsql-hackers@postgresql.org Subject: Re: Default setting for enable_hashagg_disk (hash_mem) Message-ID: <20200707050239.GE4107@telsasoft.com> References: <20200703024649.GJ4107@telsasoft.com> <20200703025834.GC26235@momjian.us> <20200703030001.GD26235@momjian.us> <20200703140808.GE26235@momjian.us> <04451034b3652d8bd9f3561c90884c3fc3653901.camel@j-davis.com> <06d7cb422c25527fb4e3c5d400018ff725f85313.camel@j-davis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <06d7cb422c25527fb4e3c5d400018ff725f85313.camel@j-davis.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Jul 06, 2020 at 09:57:08PM -0700, Jeff Davis wrote: > > I think that we should offer something like hash_mem that can work as > > a multiple of work_mem, for the reason that Justin mentioned > > recently. > > This can be justified as something that more or less maintains some > > kind of continuity with the old design. > > Didn't Justin argue against using a multiplier? > https://postgr.es/m/20200703024649.GJ4107@telsasoft.com I recanted. https://www.postgresql.org/message-id/20200703145620.GK4107@telsasoft.com -- Justin