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 1oY095-0005dl-K1 for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Sep 2022 07:15:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oY093-0000sb-JN for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Sep 2022 07:15:45 +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 1oY093-0000sS-7W for pgsql-hackers@lists.postgresql.org; Tue, 13 Sep 2022 07:15:45 +0000 Received: from mail-pf1-x431.google.com ([2607:f8b0:4864:20::431]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oY08x-0000m5-IX for pgsql-hackers@lists.postgresql.org; Tue, 13 Sep 2022 07:15:44 +0000 Received: by mail-pf1-x431.google.com with SMTP id e68so10914790pfe.1 for ; Tue, 13 Sep 2022 00:15:39 -0700 (PDT) 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; bh=bOquZ3klw4nd+OXLtCZSYtgrWRaM29o09kFAO2++5hk=; b=AghNklES9ntDCk7P8PObVEdjma3zp8ekga2nREXy05iw6RFBrfLc7JNrH3auZpkVdz +y7Rf329YIh1eNXablMjWp8ACIic4vnmQObEt+pHHA0HroLAxRBoLgTMgDT2aUg5VYus qNjTDUPvnPqZC2xwbeay9RoV5t4kVosxDoKvp3mYX2DxsngIqyv+bSe0H6+r3j2EdXmm vJMzQQ6X95SH04vU2C+q1eOEQRPsI9cApum/1Hyp9zpOqVhVvPAINko2EXORwYtiZxkB 8X6SOPym/BZy0zZXuoTBnFqLQYLEgAzBmfAisoHzDCEcjwltBz7jnLhKgGZOZ4mnEddF A4tw== 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; bh=bOquZ3klw4nd+OXLtCZSYtgrWRaM29o09kFAO2++5hk=; b=4dpaLkf8WhVeP3IQOTBL0RDnZ111k3whGpYCYMrOPwK3Ixizxm6VguY+o6cdrKplzM v8Y9MO6IkIa+NS5lmJ95u9rULOC3Bu1VjMxiqs+D4znVNjACCADEfk/kXxeF7HYLI1IR 0vFyfyjQ0TYoVh7iX7aZG24FnXQUYW//bZwV80NK4Dt10l6qkcUHq76AhlwofQ4tQulg 6PSbZe95gAulPUSRwvFhUPJAlJQ+Yl0/56G8ux2oQAHUB/YL1zhyWrIRk2q08Drfjz84 LWEz1mIW9u8ls7l28A2N/hEcbgQp3/Ebu9QTZE8cPwo1exvSyLd7zHGgLVcIq6+S7MVy b9wQ== X-Gm-Message-State: ACgBeo2IEBWv+mTQ4qfR0SUiQdsT5jBb4j546zi7jhNyd3MWSDEhFnL6 J4pj+1snlzRM5hC2nqGvpdg= X-Google-Smtp-Source: AA6agR76V1SirxpLsQ2Nyq5r9EeZ5KxYGlJDprkZSi8K/10xdd1F0sDmtRCXVWfnxLmvThMvEW4wVQ== X-Received: by 2002:a63:1e44:0:b0:42a:d7a4:48b8 with SMTP id p4-20020a631e44000000b0042ad7a448b8mr27580880pgm.52.1663053337424; Tue, 13 Sep 2022 00:15:37 -0700 (PDT) Received: from localhost (KD036014041111.ppp-bb.dion.ne.jp. [36.14.41.111]) by smtp.gmail.com with ESMTPSA id q7-20020a170902a3c700b00176dc72ad88sm7351809plb.287.2022.09.13.00.15.35 (version=TLS1_3 cipher=TLS_CHACHA20_POLY1305_SHA256 bits=256/256); Tue, 13 Sep 2022 00:15:36 -0700 (PDT) Date: Tue, 13 Sep 2022 16:15:34 +0900 (JST) Message-Id: <20220913.161534.1763577367544098635.horikyota.ntt@gmail.com> To: andres@anarazel.de Cc: jchampion@timescale.com, y.sokolov@postgrespro.ru, dilipbalaut@gmail.com, rjuju123@gmail.com, pgsql-hackers@lists.postgresql.org Subject: Re: Error "initial slot snapshot too large" in create replication slot From: Kyotaro Horiguchi In-Reply-To: <20220913.154507.1031550660908356731.horikyota.ntt@gmail.com> References: <20220719.115506.1518451006264600540.horikyota.ntt@gmail.com> <20220912215156.zi52zu6n7od3k3v3@awork3.anarazel.de> <20220913.154507.1031550660908356731.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 At Tue, 13 Sep 2022 15:45:07 +0900 (JST), Kyotaro Horiguchi wrote in > At Mon, 12 Sep 2022 14:51:56 -0700, Andres Freund wrote in > > This sees a tad misleading - the previous snapshot wasn't borken, right? > > I saw it kind of broken that ->xip contains sub transactions. But I > didn't meant it's broken by "correct". Is "proper" suitable there? No. It's not broken if it is takenDuringRecovery. So this flag can be used to notify that xip can be oversized. I realized that rbtxn_is_known_subxact is not reliable. I'm redirecting to oversized xip. Pleas wait for a while. regareds. -- Kyotaro Horiguchi NTT Open Source Software Center