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 1neEVt-0008HL-Vp for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Apr 2022 11:16:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1neEVr-0003z2-T0 for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Apr 2022 11:16:47 +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 1neEVr-0003yt-JT for pgsql-hackers@lists.postgresql.org; Tue, 12 Apr 2022 11:16:47 +0000 Received: from mail-yw1-x1134.google.com ([2607:f8b0:4864:20::1134]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1neEVl-000450-Ig for pgsql-hackers@lists.postgresql.org; Tue, 12 Apr 2022 11:16:47 +0000 Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-2eafabbc80aso196657557b3.11 for ; Tue, 12 Apr 2022 04:16:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SnMWuOX+tsctbOs1tCbcKP/FwjKTNkkQCz2U+wA2Dcg=; b=RlvlaqGCgVx/r2L98wL1Fc3zep/DQMwqUz0NHpxZJHY7cLnQ4bQrPb1h2xXf2i7gWy 1DAMJSNV8tjYrWZprCgaJk+bqZx8Pw5CORbnw1lF1G4FE/2uihxgD38BGzVlialQfrCg 4sC3b7Rs/pS81zvxep2XCTBK3LGFAZIz/yAT6ZMsKDdzXFIwULtjuXU05gEqwpGm6GK2 LRYceUmJMUEKBp7rFE9zwaATrLes97ky8zMEfw0dj/Yerwm4jjrz8HPpHIw1gTatPUtD MY1DPGfwgcIQh0IbcNbt98XW7DTSVxJPGV7TxTd9/rwIfCb1Fd6zuv1A/VuBDtcSJfdO QdZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SnMWuOX+tsctbOs1tCbcKP/FwjKTNkkQCz2U+wA2Dcg=; b=vWbL2WG7geuUeKCR+gSCb7nB4i+RMzLgVGxFccKr1d+jPvT4OBNEDbbVf2jBkD2dBq DL3OygMnkOfpcufyCKXMh9X9eSzu5BRMUrJExwhTcGCrP0j5EhwDVlhJ478KS6W9grZq s1G91Eqv9rDnQgH8x87LD2daeQEe1QlmJimLuF2Jc7wb7XUv39n1hEzCB5EQqv7Llp0G b63OM3Eou+xWupS2rl1z+G06hKpLAAEhhTmmzeF3ANc9nWdt1DxBRgAgar0BDWR2Ftdu EuAM2gQva+ZpL57tEjXzkT94SORr38RADtLzd9/9iLLNxrSoORBg6DUiSVRPwyOU7J4H QbNg== X-Gm-Message-State: AOAM531id9YfW6nzoLgTfayDweXROvZdoQTk3mUJvT2i9gqeplU5btZu p8w9vYrFP8cjwor0UgcNG4k/T/VEf6Pul09PLWE= X-Google-Smtp-Source: ABdhPJxhMHRPPyRaaRHbJA7Vg60W0GUVvI6KmpiyvrDhihFaelaWdyUpOy37/J9BoWD2NFtqrPHNZa65WjXqozxtyVk= X-Received: by 2002:a81:5258:0:b0:2ec:23b4:58c4 with SMTP id g85-20020a815258000000b002ec23b458c4mr8031299ywb.305.1649762199629; Tue, 12 Apr 2022 04:16:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Amit Kapila Date: Tue, 12 Apr 2022 16:46:28 +0530 Message-ID: Subject: Re: Skipping schema changes in publication To: vignesh C Cc: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Apr 12, 2022 at 4:17 PM vignesh C wrote: > > On Tue, Apr 12, 2022 at 12:19 PM Amit Kapila wrote: > > > > > > For the second syntax (Alter Publication ...), isn't it better to > > avoid using ADD? It looks odd to me because we are not adding anything > > in publication with this sytax. > > I was thinking of the scenario where user initially creates the > publication for all tables: > CREATE PUBLICATION pub1 FOR ALL TABLES; > > After that user decides to skip few tables ex: t1, t2 > ALTER PUBLICATION pub1 ADD SKIP TABLE t1,t2; > > I thought of supporting this syntax if incase user decides to add the > skipping of a few tables later. > I understand that part but what I pointed out was that it might be better to avoid using ADD keyword in this syntax like: ALTER PUBLICATION pub1 SKIP TABLE t1,t2; -- With Regards, Amit Kapila.