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.94.2) (envelope-from ) id 1v1heC-00Bary-AP for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Sep 2025 08:48:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v1he9-001Pas-Sz for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Sep 2025 08:48:13 +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.94.2) (envelope-from ) id 1v1he9-001Pak-Ec for pgsql-hackers@lists.postgresql.org; Thu, 25 Sep 2025 08:48:13 +0000 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v1he7-002Ki2-19 for pgsql-hackers@lists.postgresql.org; Thu, 25 Sep 2025 08:48:12 +0000 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-71d6014810fso6363017b3.0 for ; Thu, 25 Sep 2025 01:48:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1758790091; x=1759394891; 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=BKF4VhBIsT+aZqIApPRNCP6hGQiZhtM2q+nk8jctNHw=; b=Lqid4ntjxzECHntr10pz/sj7ZIv7Mvte/PWeLa7K5KiTTPepTdmDCRYT94Ejg4npvC 6ZitJW9n9auxNPEB7lBaPSuPwY0TqVZKqFKVKlH8Dcv5ylG+IliFAJJCTqJNJtS51ZxU 4QVWyZXL3oZ7FMvmcscOMXBpNAm9MeFQgUmfEq9gI3dfCOLyY65bzVOoU1giccXQ6+Ki RG5tEow7IpoWV3GQDOz+mm/rmtTCq1XTmTv0ctGekHTkewXMrIhrJNceN1oclNC3jTGG WLci1/yhCdtsDX2/0OlTYA/u2yx2qqjEu7tXjX+zoGf02RTMtTF+ua/GMOxHJda4NIe5 ysLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758790091; x=1759394891; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BKF4VhBIsT+aZqIApPRNCP6hGQiZhtM2q+nk8jctNHw=; b=ecHNn6naSUemjpc2Er82Uf6InSk91wVxabm0u2cv2YJYcLCJbyF3GM8TTi8fpI5RHS /2EawcuvuPG+p9mueJwkZI/B0hsvnlHXSNpnx3FgtvkMwVgkxC4A0Q1mCwSjs8999VD+ 2B9n52XR3FuKTrO6WSlXKTMGDJWwMqhlbxHFOYwMMxuGIdTVMmDws1BTA73vpKz+pL9G 9hgCl4iyHJLETnvU/B2u7LMeKMn+cHTmXsvtvcxXC6Z2mwJ1s/qNOqMjEUxxS65lr02q ya1sv8efFTelB9HJh13JSkFPwWPizYyhTF3kMqkia6Lnj8W35zaHup/ZHCJHEdt9bcXh c8uQ== X-Forwarded-Encrypted: i=1; AJvYcCUOetpWSi8Ct7bJepuP+h+nipIAHbSZbaJUSAc+XMXnRN+Sv5wibJzj7QAncxxA80Navagr/eD9xV2Pv3ws@lists.postgresql.org X-Gm-Message-State: AOJu0YxPfXyGcUeKq4AUWvHtiPsT/JtcrUS/atk7tXH78//l2sSu2DfF zR+ZgVMcnfSdKGTPU+Ay+clYAJby0CpAS1gFFG4ddFEXni7v/A6Cfv4K0cbsm1BLSTxwLav2zux 5ycxeCzh5m3Y3x1oBrOmSB95/RxQwHiQ= X-Gm-Gg: ASbGnctWOgoEdIIBPHWvxKrkqqtpoe59mu8fyFV8dQTNjQL1umAo5pGkOCeWdx+mLuI 1kEsRpM5OOgf6ho1B+62117ICLqc5si4vwF47eRNKUjaZ2BZrTOScPuZfhtSM7AFi6EwVdRHi5h t/W9kvR7/mJm/p/VmeH/xW+zBe0Z44fTmgvfowj1Hsrqmp5xyvLpcU4/ofJAkiAii0vPuEHDNYy 0lTc0ZMnv9EEmHcZDXF3HEF/cULB7qrjK0cSZQj5Q== X-Google-Smtp-Source: AGHT+IEzy0rm73k4czPIFMafJuUBRbZm15k89s0+Lb78TYWJAGrTKKYeH64nfFTMvsUCEi/6xAizUpjaUdpY3F/RSEM= X-Received: by 2002:a05:690c:4513:b0:732:a188:ce83 with SMTP id 00721157ae682-763fb0a6fb0mr21945067b3.4.1758790090853; Thu, 25 Sep 2025 01:48:10 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: vignesh C Date: Thu, 25 Sep 2025 14:18:04 +0530 X-Gm-Features: AS18NWBhgK0XfZE6ZJjf4eZ0WlORtWFXyBKRzvWwI21tx8PBFQVksXnB_v1J93o Message-ID: Subject: Re: Skipping schema changes in publication To: Shlok Kyal Cc: Peter Smith , 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, 5 Sept 2025 at 11:57, Shlok Kyal wrote: > > On Mon, 25 Aug 2025 at 13:38, Shlok Kyal wrote: > > > > On Thu, 21 Aug 2025 at 05:33, Peter Smith wrote: > > > > > > Hi Shlok, > > > > > > I reviewed your latest v20-0003 patch and have no more comments at > > > this time; I only found one trivial typo. > > > > > > ====== > > > src/bin/psql/describe.c > > > > > > 1. > > > + /* > > > + * Footers entries for a publication description or a table > > > + * description > > > + */ > > > > > > Typo. /Footers entries/Footer entries/ > > > > > > > I have fixed it and attached the updated patches > > > The patches were not applying on HEAD and needed a Rebase. Here is the > rebased patches Consider the following scenario: create table t1(c1 int, c2 int); create publication pub1 for table t1 except (c1, c2); In this case, the publication is created in such a way that no columns are included, so effectively no data will be replicated to the subscriber. However, when attempting an UPDATE, the following error occurs: postgres=# update t1 set c1 = 2; ERROR: cannot update table "t1" because it does not have a replica identity and publishes updates HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE. Is this behavior expected? Regards, Vignesh