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 1nCz9A-000057-Hy for pgsql-hackers@arkaria.postgresql.org; Thu, 27 Jan 2022 07:24:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nCz99-0003HM-Ed for pgsql-hackers@arkaria.postgresql.org; Thu, 27 Jan 2022 07:24:43 +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 1nCz99-0003HC-3w for pgsql-hackers@lists.postgresql.org; Thu, 27 Jan 2022 07:24:43 +0000 Received: from mail-pj1-x1030.google.com ([2607:f8b0:4864:20::1030]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nCz96-000270-Iu for pgsql-hackers@lists.postgresql.org; Thu, 27 Jan 2022 07:24:42 +0000 Received: by mail-pj1-x1030.google.com with SMTP id s61-20020a17090a69c300b001b4d0427ea2so6689589pjj.4 for ; Wed, 26 Jan 2022 23:24:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:message-id:to:cc:subject:from:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=VLJMJOAuN4/tHOzuCuv5SVYyy76oUe3h80hm55wt/7g=; b=AFFBT4LyuhnSpElbPJFQKpYYHUFSlyxFFDbJ0J/HdCg2qwevlarEU+67FbwHcvFUWg E0oNxZSaLw2UrkfgfPNA3Ok1eGTOIdH/0QHm7WESMiD2gLBDNUOpZtfIJjWoRV8o3E0P FTCzAfBV/5eQYseNx3YGUohBXmsQLI1mi3g8rPiHFQdLKMr69qDwrdgnnYBwKRF2mziB tTo/XeAShJtDKV0ArN5JVQVUhGde21TT4742/P63KkTMBqkF2a9f+ADPpnMoh1eKNLQU 1QQNcvPv1AqPo00auhZuy6WcwlkI31A9aTx0r6rT11oWnpQVsedt0d1MvZTCc3Kldt+m 2kaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:message-id:to:cc:subject:from:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=VLJMJOAuN4/tHOzuCuv5SVYyy76oUe3h80hm55wt/7g=; b=tnoJ0+xsjDBRyDeoniFxx2883KS53Wl49Kyi+fcYcGG7hs/2RH3Otjc1QZIGQXO+8/ l0ilfJeaifZOvDlHCxKn16KodeCS27VTC7PrG6A1tmyeyvtrBDB/EutAg8k5/FhtGRfF XD9tdNNEqh/M5n5PyUya46ZvumEwg1L7VTbVlW5pz0m7ACCKm0cfKHHCW/RGBf2Tth4V y84MfNCD7U0NU+VQTk5zfwmh8ipNEr60EmefDHcqsudqgrUBgBtFyA1TOlVQjdA1ihGA Qhv0n7n0Jz8bpNO9AAe45cU/8R6K6oX0b6OgaOuq09ZU9dE0fmXWT2U7/Jkh141FwBbx Kuxw== X-Gm-Message-State: AOAM531HFvaA1QNtfWdtFecIlrAC34JuESYQMz2F1DuMeiTGKR02IeP3 NYgGjLjAxxCNUgas5bXFOG8= X-Google-Smtp-Source: ABdhPJxNUnk/lTboUZqe6JmY6M/INMfuVPKspw4FpLMwmmvTSAUsxvGBeZUV70M83kow3d5c0Em0XQ== X-Received: by 2002:a17:90a:694d:: with SMTP id j13mr12909524pjm.10.1643268278831; Wed, 26 Jan 2022 23:24:38 -0800 (PST) Received: from localhost (KD036014041111.ppp-bb.dion.ne.jp. [36.14.41.111]) by smtp.gmail.com with ESMTPSA id p22sm4093260pfw.139.2022.01.26.23.24.36 (version=TLS1_3 cipher=TLS_CHACHA20_POLY1305_SHA256 bits=256/256); Wed, 26 Jan 2022 23:24:38 -0800 (PST) Date: Thu, 27 Jan 2022 16:24:34 +0900 (JST) Message-Id: <20220127.162434.876092147237035105.horikyota.ntt@gmail.com> To: michael@paquier.xyz Cc: sulamul@gmail.com, rjuju123@gmail.com, andres@anarazel.de, pgsql-hackers@lists.postgresql.org Subject: Re: TAP test to cover "EndOfLogTLI != replayTLI" case From: Kyotaro Horiguchi In-Reply-To: References: <20220118.140123.342853390774842194.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 Thu, 27 Jan 2022 15:31:37 +0900, Michael Paquier wrote in > On Thu, Jan 20, 2022 at 12:13:08PM +0530, Amul Sul wrote: > > I found the cause for the test failing on window -- is due to the > > custom archive command setting which wasn't setting the correct window > > archive directory path. > > After reading this patch and this thread, I have noticed that you are > testing the same thing as Heikki here, patch 0001: > https://www.postgresql.org/message-id/52bc9ccd-8591-431b-0086-15d9acf25a3f@iki.fi > > The patch sent on the other thread has a better description and shape, > so perhaps we'd better drop what is posted here in favor of the other > version. Thoughts? pg_switch_wal() is more preferable than filling-in a large number of records as the means to advance segments because it is stable against changes of wal_segment_size. As you said, using has_restoring on initializing node_ptr is simpler than explicitly setting archive_dir from that of another node. regards. -- Kyotaro Horiguchi NTT Open Source Software Center