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 1hDtFo-0005YY-8H for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Apr 2019 16:05:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hDtFl-000808-AW for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Apr 2019 16:05:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hDtFk-0007xb-TI for pgsql-hackers@lists.postgresql.org; Tue, 09 Apr 2019 16:05:41 +0000 Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hDtFd-0007Nx-5w for pgsql-hackers@postgresql.org; Tue, 09 Apr 2019 16:05:39 +0000 Received: by mail-wm1-x344.google.com with SMTP id a184so4237522wma.2 for ; Tue, 09 Apr 2019 09:05:32 -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=IsZQbV8/3yWIaNYulPMCM9RCpHmIPhYC0jqPlCsciEQ=; b=UZgFRPYtgkRXrYbDoaYOvDS4A52sHvM3iXRheQw741mE3jzzhJC44R/lx5ztUjt2ep 5G5sBYW2V75pDSoMpbCBNGoZaaHwgrhsdT8rV/9H47povtH4/4GVyFOQlzCu9bRTxN42 3b8D5ZX9/GvjwAV0DsJvg+gQcylzSdf2BCNsWzQRu9ucQsuFX97NWntDH30ZV9jegbsN e78ov1Q3NepB6KJxl+8KS+vttS5iT5EUx4pv5e1S7wr4OhMFKSRl9LKAjP816BYZYxXl t9HgnPbR/1/RhyzXRJyeVL9BMQHBzhUypOG/6hiA3ctjxtXjDOwSL8EqKKl0+HzV0u3o R0/A== 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=IsZQbV8/3yWIaNYulPMCM9RCpHmIPhYC0jqPlCsciEQ=; b=LWUvQ6XoG8AoM+ZxuSHIydD2c2CR+fHphcyG0CxzZold2hHOLtnE65Q9XzCBRi5phs 5DGUO/Dra8mr+tOHW1JnzGzwo4Uy6H4Naql7Ud+7spZMQsEVrcUikDq96c0ZQqCrHmVG zV4h1rzJBCnBfKw2tw274n2nbT2e4MJHWgMooxU5/RXWvIRXaTRAKIGgFzPvzpd3f9th u7xG3nXhWo0k9jQHaZ22PDXalsVBWxSa/+bPNnbhAyanyniuUrP8X+cWM9pgwV6ZpZ1V NEYNqgCoRz34s8fXXReJEfKGJDupPWNIl16sNeHrZy5qbJA0sEOLSQ4hzKyPjSuUbk/g b6Rw== X-Gm-Message-State: APjAAAVsigbZTu9Ek+t1HTHQHFW+UtVjGTSX8lSeTmNl2PGZBHUJDlQF Q1y4R2FODmkyU3Nc0rlU97uvxQ== X-Google-Smtp-Source: APXvYqxTYmdKU6oSpW6gBghXKuc2rTfQ4LgB1q1W1OqqmWIK1QgNR5x77UUfZgpWIxi8nrr5Xk13Yg== X-Received: by 2002:a1c:c504:: with SMTP id v4mr23056455wmf.45.1554825927711; Tue, 09 Apr 2019 09:05:27 -0700 (PDT) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id i28sm95314225wrc.32.2019.04.09.09.05.19 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Tue, 09 Apr 2019 09:05:19 -0700 (PDT) Date: Tue, 9 Apr 2019 18:05:18 +0200 From: Tomas Vondra To: Michael Paquier Cc: Dean Rasheed , David Rowley , Kyotaro HORIGUCHI , Alvaro Herrera , Andres Freund , Thomas Munro , Bruce Momjian , Mark Dilger , PostgreSQL Hackers Subject: Re: [HACKERS] PATCH: multivariate histograms and MCV lists Message-ID: <20190409160518.olv7xji2ugw63j77@development> References: <20190326152108.GB3088@development> <20190327195507.GA21957@development> <20190330201301.GI4719@development> <20190409022918.GD1875@paquier.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20190409022918.GD1875@paquier.xyz> User-Agent: NeoMutt/20180716-1444-295967-dirty List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Apr 09, 2019 at 11:29:18AM +0900, Michael Paquier wrote: >On Sat, Mar 30, 2019 at 09:13:01PM +0100, Tomas Vondra wrote: >> Hmmm, what's the right status in the CF app when a part of a patch was >> committed and the rest should be moved to the next CF? Committed, Moved >> to next CF, or something else? > >This stuff has been around for nine commit fests, and you have been >able to finish the basic work. So I think that committed is most >appropriate so as you can start later on with a new concept, new patch >sets, perhaps a new thread, and surely a new CF entry. OK, makes sense. I'll start a new thread for the remaining pieces. cheers -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services