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 1mTti7-00048p-7T for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Sep 2021 22:30:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mTti6-0000yH-4f for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Sep 2021 22:30:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mTti5-0000y9-GE for pgsql-hackers@lists.postgresql.org; Fri, 24 Sep 2021 22:30:25 +0000 Received: from mail-ed1-x52b.google.com ([2a00:1450:4864:20::52b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mTthx-0005bw-4n for pgsql-hackers@postgresql.org; Fri, 24 Sep 2021 22:30:24 +0000 Received: by mail-ed1-x52b.google.com with SMTP id x7so26876687edd.6 for ; Fri, 24 Sep 2021 15:30:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=XUw9TuFfyy3/p9yNwS8grGsdoj+l2fvH5F86K/Pi71c=; b=GRTnjYd6w/8lxlEN6r/tWYUeF1YUj4zXrxvQmaC0kYcXrKc6xZdbCrK+OfEkwRRbsn qw57COWOWYlE69EdiambKO+ZfbBRGBleS7v4+EiywnOxy23rx/TCLJiEoSCjfF1AAsIT TTsqIcoCNvCtTYqLOox70a7c6yqXx6qJUboQ9D3RsxhHjQk2VCkg9s4LB71/9Ii8DF3C KdY+DJvu0cw2Ko8R/e9oS5agA7/FiCtsX6dRaM/Fe1+N5bTDmMtiZgsaQLuDsD40qilC 1v93dZeDDGgNQDfbEJWS2djq7N4rJQmSb9TAp6xgp0UIqSuMZII5DGPlG0N6if2opfy9 rabg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=XUw9TuFfyy3/p9yNwS8grGsdoj+l2fvH5F86K/Pi71c=; b=Vk4NxRYpMEudSaA6ovJO6onj7sOTXL3dpUcNl14yzqzd1HYr4ESEy/NaTpu2NkPCf3 UPzUt1DzahzPsKDE5MlsaeQ6/jKuTM62Bx1UiMyGncmRIwtz7m5XpRAQ2HY8SBuLNtHf ZMBMpaxjLY3cYiyQQKgx3/wqZeF6LTgiQpBmxMMbkOb3pmmYwF4bntloKcJlU9KUcJRi qil64eqmpCUoum0kDhnU1Ilfu5+QFNCycgHTblIXdsZmSi7biknYqW6cm/iNeRpD3S2e W3ONKW+7sbhfN1L/uGI+JjeKiijZh0VtBWLexGDhZrmu/GsvhtR0QoUG0nVGdBqD6HaG s7yw== X-Gm-Message-State: AOAM5327+MtQGR2IWmvlLiCSusCHYwifsmZa5rOzKZlT8OS+2scCznnA BvILUZVKtRGAhQ1tSwmGkaIJqMwMqoUYaPpz/NrUSJSuUp1JyoyXo7LhruYrmOkRD69R9LA548O AJiMsy3OyueyFM++dVYP3o8TyMh79AFC+k+FOBTVkThnGnzlrQeE7CwL2LDOM3UZxrgj+x9CZNH nhAsyl3kdqFW23dgCTZL3Twe9oXHeMQClPuy8sDfqX+CKOfx+ptcawmVs8iwg1DaNc+1DifF6PZ f1Egg0AHfSuLe5AMZzwE95Mciu/Cxfjfl+f0w== X-Google-Smtp-Source: ABdhPJy0BVj3QlUJvBz860/9u4qCK+SppwM6uYpfWpg2y1rRK/PRuBKZHmZlxLMRf3CJ9fNfokwYrw== X-Received: by 2002:a50:d9cc:: with SMTP id x12mr7873617edj.44.1632522615093; Fri, 24 Sep 2021 15:30:15 -0700 (PDT) Received: from [10.137.0.18] (ip-86-49-251-104.net.upcbroadband.cz. [86.49.251.104]) by smtp.gmail.com with ESMTPSA id k21sm211879edx.61.2021.09.24.15.30.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Sep 2021 15:30:14 -0700 (PDT) Subject: Re: Column Filtering in Logical Replication To: Alvaro Herrera Cc: vignesh C , Amit Kapila , Rahila Syed , Peter Smith , PostgreSQL-development References: <202109242224.tfcvtyvdeafb@alvherre.pgsql> From: Tomas Vondra Message-ID: <992e75b9-d70f-9172-1fa8-088dbf1e4232@enterprisedb.com> Date: Sat, 25 Sep 2021 00:30:12 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <202109242224.tfcvtyvdeafb@alvherre.pgsql> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 9/25/21 12:24 AM, Alvaro Herrera wrote: > On 2021-Sep-24, Tomas Vondra wrote: > >> But that's not the column filtering patch, right? Why would this patch >> depend on "schema level support", but maybe the consensus is there's some >> common part that we need to get in first? > > Yes, the grammar needs to be common. I posted a proposed grammar in > https://www.postgresql.org/message-id/202109241325.eag5g6mpvoup%40alvherre.pgsql > (this thread) which should serve both. I forgot to test the addition of > a WHERE clause for row filtering, though, and I didn't think to look at > adding SEQUENCE support either. > Fine with me, but I still don't know which version of the column filtering patch should I look at ... maybe there's none up to date, at the moment? > (I'm not sure what's going to be the proposal regarding FOR ALL TABLES > IN SCHEMA for sequences. Are we going to have "FOR ALL SEQUENCES IN > SCHEMA" and "FOR ALL TABLES AND SEQUENCES IN SCHEMA"?) > Should be "FOR ABSOLUTELY EVERYTHING IN SCHEMA" of course ;-) On a more serious note, a comma-separated list of objects seems like the best / most flexible choice, i.e. "FOR TABLES, SEQUENCES IN SCHEMA"? regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company