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.92) (envelope-from ) id 1jIZqq-0000CV-B9 for pgsql-hackers@arkaria.postgresql.org; Sun, 29 Mar 2020 15:27:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jIZqm-0007uO-Ma for pgsql-hackers@arkaria.postgresql.org; Sun, 29 Mar 2020 15:27:48 +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 1jIZqm-0007uH-63 for pgsql-hackers@lists.postgresql.org; Sun, 29 Mar 2020 15:27:48 +0000 Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jIZqf-0003Lu-6g for pgsql-hackers@lists.postgresql.org; Sun, 29 Mar 2020 15:27:46 +0000 Received: by mail-wm1-x342.google.com with SMTP id z18so16989986wmk.2 for ; Sun, 29 Mar 2020 08:27:40 -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=PWMwcW73KM9R8A/P7xm9m4J2QKxAYbKUhrVNh6+pWsE=; b=rtKWjzBfNgt16zwotaVbtN6KMOWdgQWCN/JbCWP8ny23B2L6COBMXOD72rTBmaCgx/ +ZqC5TqWKYhGheRf4dufS+I4QHxbcbUqycsYCoZXyC9WSVroCgGeprWEk3G/yTuztdw7 +iDbIVwI0IoE6D1CpKdhcFhC0MY262UFq2JvU6qn3OGlZLG5ZjL3+1p5Lx+BX7qF5lyg nwOAVfByHZAT0z7DRtWlRsm3o59KYhWA34a5NgsFWxLhwvrqfzfdWFs4K0VVwAFwRWkc tyTqPmKSAxcP48UTO53OorwDykUYlbfq8A9jhTEgk2mLmazBxxEBZ14sVSMJBDgkwOZ+ hlgA== 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=PWMwcW73KM9R8A/P7xm9m4J2QKxAYbKUhrVNh6+pWsE=; b=tQMHJTGLSvYQ1505/Vioi72h8yfXgFRFOWq4muDPlleqLnzMCSzTgBS6nbLcHsuBkI 72/Pnv5XKJasYqSMbGAbCwbWQvLcGzQYlp+79try1hszZuaNuv3pvzEiHDMEl7pbgieP 84I8PSpDypPpJEV/YXb1r2d/hmfITRYCeLBAojeCfePPI9Wj416VugAP9X+KVBWvWMUn D9cqoUZEAfh7uL1QDNecCigS2EhXkfbo63zbGAbH/PFA/n6AE2LT2SU7ICaeg+XTi3QA DSqSJhViJjP55XyPGJbk27TVJPn9CVEURa/pnqyz4dQ9jy4IbvSTt6IuZk+9BMeSUDQl JEhw== X-Gm-Message-State: ANhLgQ1Fxa3ZarD8NWjS+9h03rn97JzktTKCoe5r6xrG2EcK2DzhIeLA qmP+18mobXioBUURzMF9k2YlEQ== X-Google-Smtp-Source: ADFU+vtsONla9FJH/UISuRy3wK1eALxjjThIxVbHE6bvnn7hGBqpiGwc1keWnegyYFKZXlv87r6T8g== X-Received: by 2002:a1c:b4c6:: with SMTP id d189mr8547492wmf.132.1585495659587; Sun, 29 Mar 2020 08:27:39 -0700 (PDT) Received: from localhost (ip-86-49-253-141.net.upcbroadband.cz. [86.49.253.141]) by smtp.gmail.com with ESMTPSA id t81sm17181114wmb.15.2020.03.29.08.27.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 29 Mar 2020 08:27:38 -0700 (PDT) Date: Sun, 29 Mar 2020 17:27:36 +0200 From: Tomas Vondra To: Dean Rasheed Cc: Pierre Ducroquet , PostgreSQL Hackers Subject: Re: PATCH: add support for IN and @> in functional-dependency statistics use Message-ID: <20200329152736.3c3m4geltlbepvmh@development> References: <20200314184535.4jgkxcyg5yprvsra@development> <20200317153706.z6pdtijr25iyr424@development> <20200317170517.hutarq3sioyny3wa@development> <20200318002946.6dvblukm3cfmgir2@development> <20200325002801.i45f34l45rqmik4v@development> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sun, Mar 29, 2020 at 10:22:25AM +0100, Dean Rasheed wrote: >On Sat, 28 Mar 2020 at 13:18, Dean Rasheed wrote: >> >> OK, I've pushed that with your recommendation for that function name. >> > >Does this now complete everything that you wanted to do for functional >dependency stats for PG13? Re-reading the thread, I couldn't see >anything else that needed looking at. If that's the case, the CF entry >can be closed. > Yes. There were two improvements proposed, we've committed one of them (the IN/ANY operator handling) and the other (containment) needs more discussion. So I think it's OK to mark this either as committed or maybe returned with feedback. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services