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 1oDPHG-0004cy-Jn for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jul 2022 11:51:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oDPGG-00069S-DK for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jul 2022 11:50:04 +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 1oDPGG-00069I-1S for pgsql-hackers@lists.postgresql.org; Mon, 18 Jul 2022 11:50:04 +0000 Received: from mail-yw1-x112e.google.com ([2607:f8b0:4864:20::112e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oDPG8-0003AU-NG for pgsql-hackers@lists.postgresql.org; Mon, 18 Jul 2022 11:50:03 +0000 Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-31c89653790so103523797b3.13 for ; Mon, 18 Jul 2022 04:49:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xSpW/3CHSt/nLMS7NmSkoPlOLgS9TdcLJ7yPCwdi/n4=; b=VYTVlu8aXzDxW7GXVkoy7wZBJtdnp3y9CVPxSkgV3Buraw4wISYiYYugbuLqGz8dZC gKagPb8H2kmistWacZDKVpBnsjywU2UI/RCcAZCx5KVaKZCdZB7rh4qrMsHbNbnDHHq4 p1FIgiWK9JoIU23oaLGckfT+kpb/to5zlAGkXUA4IdajWtsEdLvV0l8KbUqT0dWNo/pH QSVwks/45B2AC78K0P1OF4k0Saf7sWWrsOUzcPgQyz7WDg2YFyKva8zXAWaxvhbmlKeO phd/Ns8mvCmDldnSYJKLon9Mw3NDKhbaM254ugeC6B7Z6le6wWYlOWWZK24oFyjFHJ63 nNnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xSpW/3CHSt/nLMS7NmSkoPlOLgS9TdcLJ7yPCwdi/n4=; b=mFklR6WCNAZW2S4dAZ/2hDcC5Zq79lAMbY9qtmyyojsLrrJcs6OXQAlxWAsbA1vHop vIndiUTmBQNBT2J2XhD7UKgRrZ80kw5T/T7Q4DpzDp5a8/3P/hmNZogxdH52FDJf/jkt pYf4URtay4oSaar2D5BYJD1zCYBhtSJEzelqGtn3p2tce1Wd1c8zPdV/2fomlWtwLNqX YCDjgrpU852TPhk0mjMfdeV2cVE7KUtv1kVi6HX8Ol3vr4H/Lv0kX0mH8SixRZ4woY71 ytDBXaosuxQV/xEd714ewPtUIamoYr1VnkKC0ZKyFRsuwC2h5FU7O32Nue4+5LcV9+M0 F3jQ== X-Gm-Message-State: AJIora/m1gxAOgxwUO/zAsEzyBk9TMRIWhGj07PXO9JYvffn5duM9sqI pTvW8v5kPaqEEq/TX4oldjGECRxJOabVbJULaJc= X-Google-Smtp-Source: AGRyM1sDKHdrt+gPdTppyZrVvPDcVlbHTiO73Tp+hMgqrERI9v97gLo+nWUg7ZGNLtbH/9QXunJeF+EbwAmdjeY1ffA= X-Received: by 2002:a81:1c0e:0:b0:31c:c207:c5ab with SMTP id c14-20020a811c0e000000b0031cc207c5abmr28805199ywc.182.1658144993600; Mon, 18 Jul 2022 04:49:53 -0700 (PDT) MIME-Version: 1.0 References: <20211008.165055.1621145185927268721.horikyota.ntt@gmail.com> <20220523.133323.444599955292141474.horikyota.ntt@gmail.com> In-Reply-To: From: Amit Kapila Date: Mon, 18 Jul 2022 17:19:39 +0530 Message-ID: Subject: Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns To: Masahiko Sawada Cc: "shiy.fnst@fujitsu.com" , Kyotaro Horiguchi , "Drouvot, Bertrand" , PostgreSQL Hackers , "Oh, Mike" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Jul 17, 2022 at 6:29 PM Masahiko Sawada wrote: > > On Fri, Jul 15, 2022 at 3:32 PM shiy.fnst@fujitsu.com > wrote: > > > > I've attached patches for all supported branches including the master. > For back branch patches, * Wouldn't it be better to move purge logic into the function SnapBuildPurge* function for the sake of consistency? * Do we really need ReorderBufferInitialXactsSetCatalogChanges()? Can't we instead have a function similar to SnapBuildXidHasCatalogChanges() as we have for the master branch? That will avoid calling it when the snapshot state is SNAPBUILD_START or SNAPBUILD_BUILDING_SNAPSHOT -- With Regards, Amit Kapila.