Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u0doe-004yUa-Ea for pgsql-hackers@arkaria.postgresql.org; Fri, 04 Apr 2025 09:58:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u0dod-00G42w-4f for pgsql-hackers@arkaria.postgresql.org; Fri, 04 Apr 2025 09:58:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u0doc-00G42n-Ot for pgsql-hackers@lists.postgresql.org; Fri, 04 Apr 2025 09:58:22 +0000 Received: from meesny.iki.fi ([2001:67c:2b0:1c1::201]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u0doa-002tcn-17 for pgsql-hackers@lists.postgresql.org; Fri, 04 Apr 2025 09:58:21 +0000 Received: from [192.168.1.112] (iptv-hkibng21-58c090-167.dhcp.inet.fi [88.192.144.167]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: hlinnaka) by meesny.iki.fi (Postfix) with ESMTPSA id 4ZTYvX13CHzyQX; Fri, 4 Apr 2025 12:58:16 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1743760696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DRpBHZSgr+Bk5Y1aqHpQ1oGNXa+kbyA5Y6QfdPmdEG8=; b=P06es9n0VMz32tPE+jH+nIs/b8Ze8Ot6KCkn+VzUYwDbcAnb70sw+37UAAN7G9Zbb+jo2B VblDFHGgrN2lCrNcU5OKuJycMH3sRjclW8S74z2f2sPw8jb3oYuieLXDnpp1sXS6nUOupn hTUaS8OfoiJpASp7gLBm/wO2W65bAfg= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1743760696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DRpBHZSgr+Bk5Y1aqHpQ1oGNXa+kbyA5Y6QfdPmdEG8=; b=XBQENuKP99bfofyVH8l8+VWfUWXaIAMF1RJAjyTsB9XKUz0iLOKIWbn9SY5dDW665OBxJB aeL1aRXDzEYYprrOqUBjq5yglP55zlUcz+P9madFaID9f0aaWI+4VwH+EljDgMQ90MJHi1 LyaXdyN50+l+7vr2dLkHjCXt7YMVcrU= ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=hlinnaka smtp.mailfrom=hlinnaka@iki.fi ARC-Seal: i=1; s=meesny; d=iki.fi; t=1743760696; a=rsa-sha256; cv=none; b=IVKDcIpwRip9LRu5TQiHPO9qgw5hk/h+RsBlefju3iX8EbJam/vtc41Of8SXu8WHoZYRQy vJ5nKCRtKqeFwO/AFQf3+gGGfAB4cYALFcALJHxfVIOp9Uc/TFn/l+Hi/VPL0i/jAchFxv BEHzQtJJWQHyQ7MQePokpf2J+qg0c5c= Message-ID: Date: Fri, 4 Apr 2025 12:58:15 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Heikki Linnakangas Subject: Re: Network failure may prevent promotion To: Yura Sokolov , Robert Haas , Kyotaro Horiguchi Cc: masao.fujii@gmail.com, andres@anarazel.de, michael@paquier.xyz, pgsql-hackers@lists.postgresql.org References: <20240123.172410.1596193222420636986.horikyota.ntt@gmail.com> <20240129.163206.738744107103873975.horikyota.ntt@gmail.com> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 21/03/2025 15:24, Yura Sokolov wrote: > I've just rebased patches and merged last two fix-commits (0003 and 0004) > into 0002. Thanks for reviving this! I looked over this again and committed. On May 14, 2024 at 14:16 Robert Haas wrote: > I think it would be helpful to make it more clear exactly what's going > on here. It looks 0001 is intended to revert > 21ef4d4d897563adb2f7920ad53b734950f1e0a4, which was itself a revert of > 728f86fec65537eade8d9e751961782ddb527934, and then I guess the > remaining patches are to fix up issues created by that commit, but the > commit messages aren't meaningful so it's hard to understand what is > being fixed. Yes, that's exactly what's going on here :-). I squashed the patches together and explained that in the commit message. > I think it would also be useful to clarify whether this is imagined to > be for master only, or something to be back-patched. In addition to > mentioning that here, it would be good to add that information to the > target version field of https://commitfest.postgresql.org/48/4748/ A lot of time and v17 release passed since you wrote this, but for sake of completeness: This is for v18 only. It's not a bug fix. There was an bug with the original commit 728f86fec6, which was resolved by reverting it in v16 and v17. This commit brings it back in v17, hopefully bug-free this time. -- Heikki Linnakangas Neon (https://neon.tech)