Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vIlVy-00DUCW-0c for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Nov 2025 10:22:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vIlVv-005G6Z-39 for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Nov 2025 10:22:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vIlVv-005G6R-1i for pgsql-hackers@lists.postgresql.org; Tue, 11 Nov 2025 10:22:15 +0000 Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vIlVt-006WwV-2D for pgsql-hackers@lists.postgresql.org; Tue, 11 Nov 2025 10:22:14 +0000 Received: by mail-oo1-xc2b.google.com with SMTP id 006d021491bc7-656bc794e97so561224eaf.2 for ; Tue, 11 Nov 2025 02:22:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762856533; x=1763461333; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mlBNyw/TVpfNYA2rnZ8XR8d5Od7E5R1lFRImWmnV9Yk=; b=MPvhnJNytxykSSATw9+sdNFCLORcdpkn9S1AlM40be5Rx21BhfobbfqB0VMErNuopv Rs4bpuxKhTdHUmnf6QbqtKrDaMdgueMW8p6A50ciTcAC7TF+O6pPAYfZBNMvr7hxlEpk diaRtXZXZz/0ZBJmbWORB0KRLGrpo1ghYVt4V4L2rjp8Mrin8xUkldM73MoMZaE3tpiJ C4m9JQKCO7iESeeFzd9qV1VDDV7xF41X7RblmyKfZxrElYi0o24X8p6O0yI4jIv9DhPA iKteEEmB3ZI++7LqrvspToSS/Lk2LQXDnf99nEaJdLDcirjR5GceJXOcc9dIeQi2QpJW Qy3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762856533; x=1763461333; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=mlBNyw/TVpfNYA2rnZ8XR8d5Od7E5R1lFRImWmnV9Yk=; b=Tw4/N3JRRLCUU2h+qGlc6uEh/VkADvDJ6yLgv0+LW1pzH1tHimv2hDcmN+glajiZ4L nsHKszY9j1Kqs13bztE4DYdtDYro/8apSq6JhXUcHG8mkO1xEjBt1G1BWjyqKc+1z2Aw iqVr0/wL762v/pSBbTTod3WLGRs8Ghkc2rHTqwa4ZZJUXEIRl0v/+8XELiP7g6XO1F39 gXka3MR3Ej+/pTpUtjJ7KcmFzZ9TsgEvEEBscJHTDQLYyTcfK76/ZPg/5mbA6Vu6TJku KYxuz9Ge6Oi8KBp/kwa//RSMntoKq9oIRf/2lCNZj7hDBf9dt6lQat58a1f6iACIdKVa /HAA== X-Forwarded-Encrypted: i=1; AJvYcCUZEiYvOSGCwjcI69N4Z0ZVYidnfefMXBReqVecOT6C9NrUcivvOGNLfKZR6DRJBbWCPZ8/bkG1Mp9nYeo1@lists.postgresql.org X-Gm-Message-State: AOJu0Ywvpx201CIzLHVgXFikczQgE/YBnd9HE6vU8MbmlrcuXoFOmYgB QfxY4Q9f25n72lZOgIwjxYl1Gn1pBKrQWHU0CjTYbOW7F7PTT2I7EP+TfKSbzz1PD41E7hNrSSp iMSHUJd9VIEelE1Kt2YqzO0d5B4jJakk= X-Gm-Gg: ASbGncuoyrIDSa394Cac/yhR+PdN0JlUEz2a+X1935r4FTFPQ+Mz/7VcBTMAE6UG0Bs vPfTO2ZJB7HZ+IgvJWSm/bVXTb7FoJbYsdaA31MGv84Ta/X1RzIf6ECkf4mR3GqeSaLkTuNbk0N ybInNddSQu3HuAnUChPxF66ASNxs9vcqsSx57wBqPoldf6j4oKaUhQ7CRFuiuGig/txevU39HOo zDkOYDup/DyEZ0kzqbODaPYTjRc1WRf4EkUxtSx6PEFrxmU3u7qGC+P+Hq5KPASS0WxAn4cQE1V NvGinn1l X-Google-Smtp-Source: AGHT+IHG2EphEVNB3WrvTVZ/bPuelatOcI7oyVuCY4KURYKMqsbNi3s03HvA3oY96ZVxo/UwWY+Injjgi/YQeNj/P44= X-Received: by 2002:a05:6808:f8a:b0:44d:a1d3:a0c6 with SMTP id 5614622812f47-4502a1874e0mr6175946b6e.3.1762856532814; Tue, 11 Nov 2025 02:22:12 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Shlok Kyal Date: Tue, 11 Nov 2025 15:52:01 +0530 X-Gm-Features: AWmQ_bmeCWLDC3orRO9eMV-T1mXAkuR_94vvDWTAq0c3pbc3Rh_I9fJtl7e_40k Message-ID: Subject: Re: Skipping schema changes in publication To: Peter Smith Cc: vignesh C , Amit Kapila , "Zhijie Hou (Fujitsu)" , YeXiu <1518981153@qq.com>, Ian Lawrence Barwick , Bharath Rupireddy , 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 Fri, 7 Nov 2025 at 09:34, Peter Smith wrote: > > Hi Shlok. > > This is a general comment about the content of these patches. > > IIUC, the v25* patches currently are currently arranged like this: > > 0001 > - New command ALTER PUBLICATION pubname RESET; > 0002 > - Add new command: ALTER PUBLICATION pub_name ADD ALL TABLES; > - Enhance existing CREATE and the new ALTER syntax for EXCEPT tables > 0003 > - Enhance existing CREATE and ALTER syntax for EXCEPT col_list > > ~~~ > > IMO it is a bug that the ALTER PUBLICATION pub_name ADD/SET ALL TABLES > command does not already exist as a supported command. And, that is > independent of anything else you are implementing here like RESET or > EXCEPT. > > Therefore, I think that one should be 1st in your patchset; The EXCEPT > stuff then just becomes enhancements to existing syntax, which would > give a cleaner separation of logic. > > So, I am suggesting there should be 4 patches instead of 3. e.g. > > SUGGESTION > 0001 - New command: ALTER PUBLICATION pub_name ADD/SET ALL TABLES; > 0002 - New command: ALTER PUBLICATION pubname RESET; > 0003 - Enhance existing CREATE/ALTER syntax for EXCEPT tables > 0004 - Enhance existing CREATE/ALTER syntax for EXCEPT col_list > I read the previous conversation in the thread. And got an understanding that RESET was introduced so that we can have a way to remove 'EXCEPT TABLE' from a publication and after RESET we can use 'ADD ALL TABLES [EXCEPT]' to alter the list of EXCEPT TABLE. So I prefer to keep 'ALTER PUBLICATION .. RESET' as the first patch. I think since 'ADD ALL TABLES' serves our current purpose. We can add the syntax 'SET ALL TABLES' once 'ADD ALL TABLES' is in committed or in committable shape. Thanks, Shlok Kyal