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 1p4u1P-0001RQ-4k for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Dec 2022 01:23:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p4u1O-0001kL-0Z for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Dec 2022 01:23:50 +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 1p4u1N-0001kB-O2 for pgsql-hackers@lists.postgresql.org; Tue, 13 Dec 2022 01:23:49 +0000 Received: from mail-pg1-x52f.google.com ([2607:f8b0:4864:20::52f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p4u1H-0002ui-Mx for pgsql-hackers@postgresql.org; Tue, 13 Dec 2022 01:23:48 +0000 Received: by mail-pg1-x52f.google.com with SMTP id v3so9443555pgh.4 for ; Mon, 12 Dec 2022 17:23:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:from:subject:cc:to:message-id:date:from:to:cc:subject :date:message-id:reply-to; bh=BBt/OGlvBEFiZMmXno5wi3Ormle53hmlLgbKtCyJwFc=; b=htWpEq0prrztf9wcaIKeNuBzsXY4NCps1OSNFrh24V+5uEXhy2UU88l3RQLYVbw4f/ Zfo8LdfoJqTTBW+ktmJVZM/YxgoM6JC6RHKQ2vdsUs55pd3Msb0dmA4yLVn3SZ5/R9So Ozg+nPIMnAhHo8FgCpqnUT+f5nDF6kU4QGbCA39r9gMSN8R/2NkCHd9nKW3a3AiOQwv9 fF45bIOm6qw0CmfHLIELTQAOZwB7Ol6KLPvSYhqUnfKCW87DQXZ5Fq77n55PuQz7eNoq pFDT120i4lhTGH+kM0kiuSGkOMX6OoyA9cQ7xQKyBHVIIgkMBwpt0AHpOWZM4OKG89KX Iyow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:from:subject:cc:to:message-id:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=BBt/OGlvBEFiZMmXno5wi3Ormle53hmlLgbKtCyJwFc=; b=0SaVTvQN67lLVglDK5WxdiLtVqSxgMGvU1Lipd6wrWyXEfp9JUjnn/5UG2CDx5urfw lwBj82sbsnkXp8a+wbkA5uplHcKfSYmMAbJ+2rVZVILYzs7ur9HZ9Prz+wMMXweF0hwv imWzp7VBIWUGFNfjKpt1yM7tzVq6/WFwPLEHqdpw+yxx+Qm5fKW15FI7Y4nD4xzxbdC+ Gkzaoc96ipGJUtnsidorewc432cKROQyaMMWpHRJn05Qccs3IdLP+j94wcWylZX5RBaV p86ggRKOeUGSNDP6MtaDW0EVxUY0KgtopRiNz1yMGjKa+nb0pWwgWed8So+M7GC/afQE Laeg== X-Gm-Message-State: ANoB5pkoruRoYBbUjkOzydhg7oBobHA3prObM3XfIAYUZ8fpb95+iprP fulpl/LjPB0maY8Y+URlH7A= X-Google-Smtp-Source: AA0mqf5Qt3GNpnu5kzj5M7evqWTRyrdq6rQJki0KHJLlVotXjR4efKDBZF1PWmRnzNz7+Kk6sxOmVw== X-Received: by 2002:a05:6a00:18a0:b0:577:3523:bd1f with SMTP id x32-20020a056a0018a000b005773523bd1fmr21451274pfh.14.1670894622601; Mon, 12 Dec 2022 17:23:42 -0800 (PST) Received: from localhost (KD036014041111.ppp-bb.dion.ne.jp. [36.14.41.111]) by smtp.gmail.com with ESMTPSA id w16-20020a627b10000000b005636326fdbfsm6379516pfc.78.2022.12.12.17.23.40 (version=TLS1_3 cipher=TLS_CHACHA20_POLY1305_SHA256 bits=256/256); Mon, 12 Dec 2022 17:23:42 -0800 (PST) Date: Tue, 13 Dec 2022 10:23:24 +0900 (JST) Message-Id: <20221213.102324.1828051034772830254.horikyota.ntt@gmail.com> To: osumi.takamichi@fujitsu.com Cc: smithpb2250@gmail.com, euler@eulerto.com, m.melihmutlu@gmail.com, andres@anarazel.de, amit.kapila16@gmail.com, marcos@f10.com.br, pgsql-hackers@postgresql.org Subject: Re: Time delayed LR (WAS Re: logical replication restrictions) From: Kyotaro Horiguchi In-Reply-To: References: <20221212.145409.1425479535653769807.horikyota.ntt@gmail.com> User-Agent: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello. At Mon, 12 Dec 2022 07:42:30 +0000, "Takamichi Osumi (Fujitsu)" wrote in > On Monday, December 12, 2022 2:54 PM Kyotaro Horiguchi wrote: > > I asked about unexpected walsender termination caused by this feature but I > > think I didn't received an answer for it and the behavior is still exists. .. > Thank you so much for your report! > Yes. Currently, how to deal with the timeout issue is under discussion. > Some analysis about the root cause are also there. > > Kindly have a look at [1]. > > > [1] - https://www.postgresql.org/message-id/TYAPR01MB58669394A67F2340B82E42D1F5E29%40TYAPR01MB5866.jpnprd01.prod.outlook.com Oops. Thank you for the pointer. Will visit there. regards. -- Kyotaro Horiguchi NTT Open Source Software Center