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 1nYipD-0005oV-Lo for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Mar 2022 06:25:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nYipC-0004OC-0t for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Mar 2022 06:25:58 +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 1nYipB-0004O2-MH for pgsql-hackers@lists.postgresql.org; Mon, 28 Mar 2022 06:25:57 +0000 Received: from mail-pf1-x42e.google.com ([2607:f8b0:4864:20::42e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nYip9-0006sh-GR for pgsql-hackers@postgresql.org; Mon, 28 Mar 2022 06:25:56 +0000 Received: by mail-pf1-x42e.google.com with SMTP id h19so10682934pfv.1 for ; Sun, 27 Mar 2022 23:25:55 -0700 (PDT) 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=fjAzDZGhNFlcds5vDcAWhSGUcoypGbrRqsd/zMPB7bc=; b=BHoBn2Unm+kwpKwjJcbg86fsyahs8Fl999hUv2rt7xQnveBu0ag2e2I5YETvROv+FM ohSxx9ke0BSBuveEY63hj2Unb2ll+L1zs4IsO4LDViXKcKSDYFI0A3vAQT8uJUi3R7+H TT7GAhWYb2ISNjXjrsahYnrMKGFDDyrPDyz3761sb29uqEYGCdDGboYwQ/Hp5P9p3xq4 LneWc24PrPX1QkRcRY4nUyDUFnKingDVro6i6PmlPj/6UzCsgAGy5YR6T7wPi1sT6pZb P+TRSaGOcmIYZpHKCtEzeN4XEcycynauFCWf3gJp4MMgINJMuDFlFH2R/gMLOjRmoA2X ce2A== 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=fjAzDZGhNFlcds5vDcAWhSGUcoypGbrRqsd/zMPB7bc=; b=qVn3zNdRHIL+atNe1FN89EZ/OeXqG0v392eMMAuokoRIzuP0R1FPsvVIO3eJg1nPFT YTY3OpcRZKdLOsli/xBL6kbgeCzoXTobqawPjcfCQTUSy0S19XO4KA4dsm25LuNP+fOF iGzjGPt2/TrI33p420o1DPmr2dHiH+zGu2qF3JJAm+/ednl6PeTdA+/mgtTnfhgRyOwx uAnGScJC8UOzdkNaDg2RH3vKlZbbccJsNw19yfmFF3az8iuZG4i/tzwN4d/Q8Vb1a8DH 9+lxmJfuC0GvLTHQjCa+bNN8oycApNO7WQb6qnPj4RCnuiWu4KB6U9GdOvsrlrlM18bx W3PQ== X-Gm-Message-State: AOAM532b7G8dMGxGm2+FRtM4Pw3SfewjywsVktciLOC1BZx+feebi+zt pHqHLUALBdt+aUmC9CVAnOr8PZELGz4= X-Google-Smtp-Source: ABdhPJyUdQra29X7wwnKjHDdyNchtu3SCFV84E75grs/FoLw/r5sZnGY7mntLW5YZ+p4K8XJ07iZGQ== X-Received: by 2002:a05:6a00:194c:b0:4fb:32b9:dfb6 with SMTP id s12-20020a056a00194c00b004fb32b9dfb6mr9104489pfk.17.1648448754379; Sun, 27 Mar 2022 23:25:54 -0700 (PDT) Received: from localhost (KD036014041111.ppp-bb.dion.ne.jp. [36.14.41.111]) by smtp.gmail.com with ESMTPSA id p3-20020a056a000b4300b004faee36ea56sm13969756pfo.155.2022.03.27.23.25.52 (version=TLS1_3 cipher=TLS_CHACHA20_POLY1305_SHA256 bits=256/256); Sun, 27 Mar 2022 23:25:53 -0700 (PDT) Date: Mon, 28 Mar 2022 15:25:51 +0900 (JST) Message-Id: <20220328.152551.1598976250178471352.horikyota.ntt@gmail.com> To: thomas.munro@gmail.com Cc: alvherre@alvh.no-ip.org, michael@paquier.xyz, rjuju123@gmail.com, pgsql-hackers@postgresql.org Subject: Re: standby recovery fails (tablespace related) (tentative patch and discussion) From: Kyotaro Horiguchi In-Reply-To: References: <202203251226.gtrffvumu2qg@alvherre.pgsql> <20220328.100105.1221496055249686192.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 Mon, 28 Mar 2022 14:34:44 +1300, Thomas Munro wrote in > On Mon, Mar 28, 2022 at 2:01 PM Kyotaro Horiguchi > wrote: > > At Fri, 25 Mar 2022 13:26:05 +0100, Alvaro Herrera wrote in > > > Pushed this, backpatching to 14 and 13. It would have been good to > > > backpatch further, but there's an (textually trivial) merge conflict > > > related to commit e6d8069522c8. Because that commit conceptually > > > touches the same area that this bugfix is about, I'm not sure that > > > backpatching further without a lot more thought is wise -- particularly > > > so when there's no way to automate the test in branches older than > > > master. > > Just a thought: we could consider back-patching > allow_in_place_tablespaces, after a little while, if we're happy with > how that is working out, if it'd be useful for verifying bug fixes in > back branches. It's non-end-user-facing testing infrastructure. I appreciate if we accept that. The patch is simple. And it now has the clear use-case for back-patching. regards. -- Kyotaro Horiguchi NTT Open Source Software Center