Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i8n41-0003h8-NE for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Sep 2019 15:00:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i8n40-00077J-K5 for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Sep 2019 15:00:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i8n40-00077A-BD for pgsql-hackers@lists.postgresql.org; Fri, 13 Sep 2019 15:00:44 +0000 Received: from mail-wr1-x444.google.com ([2a00:1450:4864:20::444]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i8n3x-0003uz-OZ for pgsql-hackers@lists.postgresql.org; Fri, 13 Sep 2019 15:00:43 +0000 Received: by mail-wr1-x444.google.com with SMTP id l11so32387706wrx.5 for ; Fri, 13 Sep 2019 08:00:41 -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:user-agent; bh=7aGH/KoY13tSrlEFw0INhbfyAuY9etCS1zJUwjvaAUY=; b=PFay0w6+LeNge/mQmWmDuNusY4+4wF3j5jFYc9txF7kfTsVyDsoFwrDWkzMWUkM/+K YLALvVmfjJ3iA+r7iZW79bUN7xCwEj94HYNlqM5AJdrsaLDsegAuWeL/zHoZr2Lp503q GYJWVxvE1+ZPblJNDCEuO3dH7xqsY5JHJY3l61/OpBRblljlJc92XBMGRLPw0etqKqIQ txVLmyb1oYk2qJFQLgeZ1nHKnowd8BMvD+645y4ih7mM09nYjsDny5zX8+V2EuPCIfNV FLdG9gIr2JuqJn8AlxuOuBxXgPTDWrmS2d9iXG7rnh55bECQ5BC+aUGxI0rdFefpa06A 89xA== 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=7aGH/KoY13tSrlEFw0INhbfyAuY9etCS1zJUwjvaAUY=; b=nJfc1Vw/WFgroUUFmfXy9YspBZ0+BUyR5746VVpTX4LeJJQ4iAIl4QrCA4ElkPGg7t 0Cevmwfmkz819atDTbk4Ke9oQQ/kjHSiiCJMz1Qlqv/lVhEw9lsMgKDONe9sBX//7zb9 bQ5O4neQdhZIh5t1b5kioCs5HZrWTuz9ydH313UfwEsvIySmvxaIMTIAr0frXhAzMkag c1OyiP9cjZ7RIMUvC6ow57lNuw/A9aQSp4AyTvCT4b9mawr+iZEiM6+QETHtjwKm4jao 9sc64vNr7IZJjuC9CtEcpDxO66VVit04kgiAhmIjoFRK8t58C5YkHJ9Ez+eGneJkcY4K xePQ== X-Gm-Message-State: APjAAAXeRmrGxPkEFKAYYnjDDIqvvvXLRqMsHgkRnlH8mPiwLmi6S5Tm c/esrXWU14O6CrbF+a4vJJVSScdsn3I= X-Google-Smtp-Source: APXvYqwmFMwGw6D7ZFEojsXxYz0vH7iyjR4tv8f1coMdJ4Cq1xxbUgEK28os5yEi9/CtkSWzSKBzDQ== X-Received: by 2002:adf:f150:: with SMTP id y16mr916053wro.71.1568386497174; Fri, 13 Sep 2019 07:54:57 -0700 (PDT) Received: from localhost (ip-86-49-253-183.net.upcbroadband.cz. [86.49.253.183]) by smtp.gmail.com with ESMTPSA id y186sm4971579wmb.41.2019.09.13.07.54.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 13 Sep 2019 07:54:56 -0700 (PDT) Date: Fri, 13 Sep 2019 16:54:55 +0200 From: Tomas Vondra To: James Coleman Cc: Alvaro Herrera , Peter Geoghegan , Simon Riggs , Rafia Sabih , Shaun Thomas , Dmitry Dolgov <9erthalion6@gmail.com>, Alexander Korotkov , Tom Lane , PostgreSQL Developers Subject: Re: [PATCH] Incremental sort (was: PoC: Partial sort) Message-ID: <20190913145455.7buvdgqraulps76i@development> References: <20190730001711.hprrcx3ntk57wuqv@development> <20190912154929.GA2254@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716-1444-295967 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Sep 12, 2019 at 11:54:06AM -0400, James Coleman wrote: >> OK, so we have that now. I suppose this spreadsheet now tells us which >> places are useful and which aren't, at least for the queries that you've >> tested. Dowe that mean that we want to get the patch to consider adding >> paths only the places that your spreadsheet says are useful? I'm not >> sure what the next steps are for this patch. > >I wanted to note here that I haven't abandoned this patch, but ended >up needing to use my extra time for working on a conference talk. That >talk is today, so I'm hoping to be able to catch up on this again >soon. > Good! I'm certainly looking forward to a new patch version. As discussed in the past, this patch is pretty sensitive (large, touches planning, ...), so we should try getting most of it in not too late in the cycle. For example 2019-11 would be nice. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services