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 1q7HMg-0002g5-TK for pgsql-docs@arkaria.postgresql.org; Thu, 08 Jun 2023 15:15:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q7HMf-0002d9-Or for pgsql-docs@arkaria.postgresql.org; Thu, 08 Jun 2023 15:15:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q7HMe-0002c6-Tu for pgsql-docs@lists.postgresql.org; Thu, 08 Jun 2023 15:15:53 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q7HMb-000uhn-T1 for pgsql-docs@lists.postgresql.org; Thu, 08 Jun 2023 15:15:51 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 1631F5C0225 for ; Thu, 8 Jun 2023 11:15:49 -0400 (EDT) Received: from imap49 ([10.202.2.99]) by compute6.internal (MEProxy); Thu, 08 Jun 2023 11:15:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1686237349; x=1686323749; bh=sv 0BMJ17es3GOQIy4MVDdHsLqSGfCK9yDPt8j+8qCwM=; b=ODQ/kLGHF/lu4hXd1v Js9lTp61iPv9HJOcoU03yWht/dBldG20616fqNxzo0c5LIzkpFA/EalQgjndezYi vgMRcAyxsOEnu+lySLQysdGMZoJX/OwOPdrYvtDOSmuFx5jGSAHx589i2eA+QwVa 8cnbbnEIMxdaMDNTTw74PN7GasbOgBFYy6MAnL1WV+0Z2l0q76TSIOpWB6xuqIjU o8NKmwKLiP8qqQm5IFkiRacLgKxtXSQdIMFIjDTuJZsHyeUF4tbksGkNrqXBYCLs iBLh8Q8rPyl4tGr7G8Sw4fPl6xLA8ChrN/TeuHT/itBXvq0eSQPOTi9+tlhhcxaU nF2w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1686237349; x=1686323749; bh=sv0BMJ17es3GO QIy4MVDdHsLqSGfCK9yDPt8j+8qCwM=; b=rDQb4zrPZa3i5oDbQy2mbDw9GVlAT RGm0UjyFAVxZwus8jHyZ/MfuQBti73yPxEDNs4n5l9pK3CC+UNhQQkFsbmdwW8U2 zDm4OH2JRl9reCRXkqYUvw+PLevqWwr5zK6Fo9nRxD9NrOQhF0RazSc11+9eeDHd QLlnhAgOFvprTZzqJX3/oNuSfbZ/LjKAxmXWVYlP7wsoIsRin9Ndz/IWpithEcMS SXTZz4L21kfnXG+BBx7LUxh9iebB/CsBiv9tRh4ugj85K1tRYRqgTBGipiEve/bD 9K2mFcb6rYzbcJ6mlX2JiQDQTtahY9vwBDb3h98nBaEJPAp4wXyegCCkQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedtiedgkeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfgfhulhgvrhcuvfgrvhgvihhrrgdfuceovghulhgvrhes vghulhgvrhhtohdrtghomheqnecuggftrfgrthhtvghrnhepjeethfeuvdfgffdtteevud eftdejueffkeelveekhfevkeegleefhfejhedtjeegnecuffhomhgrihhnpegvnhhtvghr phhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegvuhhlvghrsegvuhhlvghrthhordgtohhm X-ME-Proxy: Feedback-ID: i0c21471d:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id B430C15A008E; Thu, 8 Jun 2023 11:15:48 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-447-ge2460e13b3-fm-20230525.001-ge2460e13 Mime-Version: 1.0 Message-Id: <288747bd-911b-4370-8db2-6ecbb096037e@app.fastmail.com> In-Reply-To: References: <5bb2c9a2-499f-e1a2-6e33-5ce96b35cc4a@postgresql.org> Date: Thu, 08 Jun 2023 12:15:28 -0300 From: "Euler Taveira" To: pgsql-docs@lists.postgresql.org Subject: Re: clarifying trigger/rule behavior on logical replication subscribers Content-Type: multipart/alternative; boundary=629b2ae694984b70ac953e83fe46f77c List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --629b2ae694984b70ac953e83fe46f77c Content-Type: text/plain On Thu, Jun 8, 2023, at 3:36 AM, Amit Kapila wrote: > I agree that it is a good idea to be explicit about this behavior. As > mentioned by you, it would be better to backpatch this. Also, I > thought about moving this to some other section like [1] but I think > we need to explain a bit about apply worker before providing this > specific information. So, the current place seems to be the best bet > considering the way current logical replication is documented. I agree with this clarification in the suggested section. One small suggestion is to avoid the word "replica", AFAICS it is not used in the logical replication chapter; use "subscriber" instead. Another suggestion is to add links to the exact ALTER TABLE ... ENABLE TRIGGER and ALTER TABLE ... ENABLE RULE since we recently added it. -- Euler Taveira EDB https://www.enterprisedb.com/ --629b2ae694984b70ac953e83fe46f77c Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Thu, Jun 8, = 2023, at 3:36 AM, Amit Kapila wrote:
I agree that it is a good idea to be explicit = about this behavior. As
mentioned by you, it would be bett= er to backpatch this. Also, I
thought about moving this to= some other section like [1] but I think
we need to explai= n a bit about apply worker before providing this
specific = information. So, the current place seems to be the best bet
considering the way current logical replication is documented.

I agree with this clarification in th= e suggested section. One small suggestion
is to avoid the = word "replica", AFAICS it is not used in the logical
repli= cation chapter; use "subscriber" instead. Another suggestion is to add
links to the exact ALTER TABLE ... ENABLE TRIGGER and ALTER= TABLE ... ENABLE
RULE since we recently added it.


--
Euler Taveira
EDB   https://www.enterprisedb.com/

--629b2ae694984b70ac953e83fe46f77c--