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 1vVRFP-003Pbj-39 for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Dec 2025 09:21:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vVRFO-005VGr-2w for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Dec 2025 09:21:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vVRFO-005VGj-1r for pgsql-hackers@lists.postgresql.org; Tue, 16 Dec 2025 09:21:35 +0000 Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vVRFM-0011EF-21 for pgsql-hackers@lists.postgresql.org; Tue, 16 Dec 2025 09:21:35 +0000 Received: by mail-oi1-x231.google.com with SMTP id 5614622812f47-450c9057988so2612107b6e.1 for ; Tue, 16 Dec 2025 01:21:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1765876890; x=1766481690; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=LlfEfFU+mKDXUwIYQZvzR3W62pD8EFpCj8XP2IrjS34=; b=cEaizvLEInRUs9IP3bMbahS8ZMzaJ1d6YDXJ1S0ZxMCFyWnAqbg+EFaWdVUxV5t/Kn 0rrtGw809vaT+ajiJyrJIvVqiZdDuw601Bd5F7sF5tvenD5GMHc0E7oBzWHfl/+sRJhF NUdhs2Wndn0rjPm/edm++VjuaycrAaYyCR3s2Qsl2ZEOljerMh8fk2FPDCN+g2nUiyRf xM/oGAOAd85ngHZfUT5c3nQuruQG8Fd9RN1QaX4XNJsE1A+MqGa+UPmF35WWhhs0l1x1 FmoyVYdhrpkv98UBzllvBkV5Rk9IQhmNEwsO7rw970V9g6X/2iQGT2vZ6AnVZEREfeEp NweA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1765876890; x=1766481690; h=content-transfer-encoding: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=LlfEfFU+mKDXUwIYQZvzR3W62pD8EFpCj8XP2IrjS34=; b=bF/9sEi1RJgNLRhBqN0g9Q87hId6Om9YRHXG32qRXAr4noO/VKrjYK9AOEmEqvs2sc YUOKHmJMA1mgghyKpGw1TRmqIX1vUZ0Yv5AEaJEbz2ag7UCG3soSTlfF91Ero4iZCPXk n/uW6w0lIkct0F8SqQqKhRiA+l1YWa2UHG29GpQi/pt2J7H9pkXDEXGMQw46s6SsWt9L i3cn3sLyFwKaSMQTPUXK4T066YBQcLIcJUlGZtYrDBo+JjM6et5qShiybkgGimzuq6Nd 49d+YxM191Orz0ejmGWshc15GeTwYpLz22TMbwXflsxm9SqFaoxuTcIZiajrv0CyXmkj LsBw== X-Forwarded-Encrypted: i=1; AJvYcCUDoyqhP3xauJXrLx8ZNLfLz+IY4nMqc9z1znRNpKyoilrr4t/S3HLtmOFPjxGoQ/QkVplHUTZ1HK5QyZK9@lists.postgresql.org X-Gm-Message-State: AOJu0Yxm84nXbkMtFYVAl8mysUtad6MEyCabRzMkBCIsymjyY4bus+dX dPF5Dkb0D4ilJGn12cal3Ig6i5jtUO8lNM7FB5wktFVRJLpBoUiborZrgPvFDTTXstgymZGzHp/ cnH6GCs52ZWfk7LFMFOvttbIn3NuMFRk= X-Gm-Gg: AY/fxX5GYJPIF2B1W3fJKERTtgn3+nWL0vgRRM6BmXSf4hE6QCzZBe4G/puQyFcSlqy 3qLKh5/7Mk8L435lVv+mFjEn/LLFHnMW6tHl5s+eRNKCwLHJoPG4Sf8rnErH1IDOlHcrFU+IbL0 2llQt69hxZRYIfnEjWKIAFAvXEe1pobXPKTAsSHw4xaVrHaSfh5qh/RQGFJ/DHwgC4T+eRnl3yz FxPlCoTSSo3QCdloAy4DlLBjbzuxUqbvELx7S7lpNJqgQ82z9Xg3YZ3dATQD2K3gB/ZAaYmoOFE dMgm42Lt X-Google-Smtp-Source: AGHT+IFpfRrndl+R3JBiQmYTOYurBtF07tNdfgTBiMkIATSiLE5X0Rnjb058wDaldT9TMlcTT+QwzpKosZyet+E14yc= X-Received: by 2002:a05:6808:4f6c:b0:43f:ac46:7ac5 with SMTP id 5614622812f47-455ac80bf21mr6184574b6e.13.1765876890277; Tue, 16 Dec 2025 01:21:30 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Shlok Kyal Date: Tue, 16 Dec 2025 14:51:18 +0530 X-Gm-Features: AQt7F2oCDeoZZorCG1kB-Nn4kxLKDIMBVyEJ3vjm6X3faWCJrRdADpe9ev-JBTw 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" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 11 Dec 2025 at 04:31, Peter Smith wrote: > > On Wed, Dec 10, 2025 at 4:49=E2=80=AFAM Shlok Kyal wrote: > > > > On Mon, 24 Nov 2025 at 13:03, Peter Smith wrote= : > > > > ... > > > 21. > > > I was wondering if the "describe" for tables (e.g. \d+) should also > > > show the publications where the table is an ECEPT TABLE? How else is > > > the user going to know it has been excluded by some publication? > > > > > I thought it would be sufficient to show only the list of > > publications, the table is part of. > > Users can check the excluded tables by checking the description of the > > publication using \dRp+. > > Will it be not sufficient? > > I am not sure why we should show a list of publications which it is not= part of? > > Am I missing something thoughts? > > For this comment, I was imagining a scenario where there are dozens of > publications, and the user is wondering why their table is not being > replicated to the subscriber like they expected it would be. > > Yes, they could use \dRs+ to identify the publications excluding it, > but that will be quite painful if there are very many publications > they have to check. IIUC, there is no other way to check it without > digging into System Catalogs. > > That's why I thought it might be useful if the \d+ could also show > publications where the table was named in an EXCEPT TABLE clause. > I thought more about this point and it can be useful. I have added the changes for the same in the latest patch in [1]. [1]: https://www.postgresql.org/message-id/CANhcyEWg2WbEW_fFwk0D3J2KBrUF7th= 6VrE%2BgvESgkUKP9VpZg%40mail.gmail.com Thanks, Shlok Kyal