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 1no3UV-0004E3-UM for pgsql-hackers@arkaria.postgresql.org; Mon, 09 May 2022 13:32:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1no3UT-00081o-Ka for pgsql-hackers@arkaria.postgresql.org; Mon, 09 May 2022 13:31:57 +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 1no3UR-00081Q-Qy for pgsql-hackers@lists.postgresql.org; Mon, 09 May 2022 13:31:57 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1no3UJ-0004by-ET for pgsql-hackers@lists.postgresql.org; Mon, 09 May 2022 13:31:55 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 7F10D320090E; Mon, 9 May 2022 09:31:42 -0400 (EDT) Received: from imap49 ([10.202.2.99]) by compute2.internal (MEProxy); Mon, 09 May 2022 09:31:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= cc:cc: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=1652103102; x=1652189502; bh=v6oj0EC5e/ moQlqEFWjhdDg7VOtyg+ZRmiaMZCfbn3c=; b=CfmTtJFNYS4FhMUCMpllxmabhm Q+z1Q/Cotw0ExeDxoj6ZntgjcWcy+DTwm3si/q6mJkgd/MHPqGnhELLtL3BGu4G6 gXDewnkzONILa6mT3+zrS9xM4FJ1tnsiOGm6pjAtLoUzd8Ugof+WLW705xHGTKfD CpkdL4sPsuy8Phxd6gb1iOzQo94c0nr0YFFJ7MZzdY+M/fhBuiF2eCrEfbgNxaNf NJX10J25717qTgzt2jtw7nWv4TvEEspA47Pb+HRbFk28BhL+wRTEsLO/N3efxZfx RVnGN3RL0gwuHI5iDYrHvswIvJ0hva8AaufGDbBGmt3eSHZOyJEOPpEDd1xQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date: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=1652103102; x= 1652189502; bh=v6oj0EC5e/moQlqEFWjhdDg7VOtyg+ZRmiaMZCfbn3c=; b=n rBtH7lprhKir6wYtaAOl+faWbyUdaA0fL2UXI6qye24EOyh+0pELMTbnbjGTkFJF BdMGaDyfuaQwi8ecwATdr2Bz1yRnRRMVVsI3FRBa5RmsQCKsSu8zJu/1wh8CmoMq zWvRq9FMOA7RiOYgHgDNq0JkJzEG7yUaAZ1TcCgb8CfeStolhMCSFwslhkKe4OwP 5/fMV2efuFBjcGCFnfuOh1rZTd5RXCa74K1q1RMMPqzXOQklo+6sMJp1EKZH7Yhg hWl0PebJ4DPIAJcdlGco124nbkFu49DQq+UyIlZQib6FJpraK2/5jlMKWkDkvDdG xCF5xLt0FZwojJ2XD1rYw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeelgdeihecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvvefutgesrgdtreerreertdenucfhrhhomhepfdfguhhl vghrucfvrghvvghirhgrfdcuoegvuhhlvghrsegvuhhlvghrthhordgtohhmqeenucggtf frrghtthgvrhhnpefgffejvdeivdekvdeivdetudeikeduieevtdfhhfduvdetgeelteei ffekgefhvdenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmnecuvehluh hsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvghulhgvrhesvghu lhgvrhhtohdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 7AB2815A0081; Mon, 9 May 2022 09:31:41 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-591-gfe6c3a2700-fm-20220427.001-gfe6c3a27 Mime-Version: 1.0 Message-Id: <78d4b56b-f6a5-4260-90a6-9943e0e88ce6@www.fastmail.com> In-Reply-To: References: Date: Mon, 09 May 2022 10:30:52 -0300 From: "Euler Taveira" To: "Amit Kapila" , "wangw.fnst@fujitsu.com" Cc: "Masahiko Sawada" , "houzj.fnst@fujitsu.com" , "kuroda.hayato@fujitsu.com" , "Peter Smith" , "Fabrice Chapuis" , "Simon Riggs" , "Petr Jelinek" , "tanghy.fnst@fujitsu.com" , "PostgreSQL Hackers" , "Ajin Cherian" Subject: Re: Logical replication timeout problem Content-Type: multipart/alternative; boundary=14c4027ab2b044eda38d4c5997312c37 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --14c4027ab2b044eda38d4c5997312c37 Content-Type: text/plain On Mon, May 9, 2022, at 3:47 AM, Amit Kapila wrote: > Thanks. The patch LGTM. I'll push and back-patch this after the > current minor release is done unless there are more comments related > to this work. Looks sane to me. (I only tested the HEAD version) + bool end_xact = ctx->end_xact; Do you really need a new variable here? It has the same name and the new one isn't changed during the execution. Does this issue deserve a test? A small wal_receiver_timeout. Although, I'm not sure how stable the test will be. -- Euler Taveira EDB https://www.enterprisedb.com/ --14c4027ab2b044eda38d4c5997312c37 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Mon, May 9, = 2022, at 3:47 AM, Amit Kapila wrote:
Thanks. The patch LGTM. I'll push and back-pat= ch this after the
current minor release is done unless the= re are more comments related
to this work.
Looks sane to me. (I only tested the HEAD version)
=

+   bool     &nbs= p;  end_xact =3D ctx->end_xact;

Do = you really need a new variable here? It has the same name and the new on= e
isn't changed during the execution.

Does this issue deserve a test? A small wal_receiver_timeout. A= lthough, I'm not
sure how stable the test will be.


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

--14c4027ab2b044eda38d4c5997312c37--