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.98.2) (envelope-from ) id 1xTHTd-00000000EYU-3fO3 for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Nov 2026 11:35:55 +0000 Received: from localhost ([127.0.0.1]:48064 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xTHTc-00000005AYQ-46Rg for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Nov 2026 11:35:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:41614) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xTHTc-00000005AYG-2XQ5 for pgsql-bugs@lists.postgresql.org; Tue, 17 Nov 2026 11:35:52 +0000 Received: from mail.zonezero.se ([46.246.30.157]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xTHTZ-00000000AAc-3nBW for pgsql-bugs@lists.postgresql.org; Tue, 17 Nov 2026 11:35:52 +0000 Received: from mail.zonezero.se (unknown [10.100.2.1]) by mail.zonezero.se (Postfix) with ESMTPS id E0962766; Tue, 17 Nov 2026 12:35:48 +0100 (CET) Received: from smtpclient.apple (host-95-193-38-246.mobileonline.telia.com [95.193.38.246]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.zonezero.se (Postfix) with ESMTPSA id 25714120003; Tue, 17 Nov 2026 12:35:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zonezero.se; s=dkim; t=1794915348; 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=LNSE8unhzYV7MEKtfF0I26+9bWR8dvfUExzR1HLoosU=; b=TS2yTU0TpmIM1cE6OuBdtB+/BPx849WFbeL47RjIuTjxD8bZQ3iSJ5lfP1b99kVUtjC10U LjM2xS35Tgv9P8PHFy3mxhnMafMD7LojonRLE0nQJ/q8OtkQE8cauT8rkLgmmQMUtxWrv2 sr4ddRQjYVj3fdpfBCZ1ksYXdCA7vm6qybruRr241zFRZ0Qk0qSuMVaf1hERFaB+9NRIdv PXW3qk/QI6JtlD2gvFcIfEqbG3bm86QA2rp2sJr/bUhvSL4eeXECPtjsKj2SbOjxROhwqr oLsloRZ2hMpc3XaPIWwiom6MKJTd5IBd/nwg4fLIs/5wRynrUSL/EXzhO9efyg== Authentication-Results: ORIGINATING; auth=pass smtp.auth=admin@zonezero.se smtp.mailfrom=admin@zonezero.se Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: Timing issue in pg_basebackup From: Jesper St John In-Reply-To: <4E8EC951-B75E-4CB8-97B6-D5C21F88A991@yandex-team.ru> Cc: Magnus Hagander , Zsolt Parragi , Jesper St John , PostgreSQL mailing lists , Kirill Reshke Date: Tue, 17 Nov 2026 12:35:37 +0100 Message-Id: <4F71E8F4-32D9-4B37-9DA9-203564F00692@zonezero.se> References: <4E8EC951-B75E-4CB8-97B6-D5C21F88A991@yandex-team.ru> To: Andrey Borodin X-Mailer: iPhone Mail (24B156) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi! Sorry, even though I=E2=80=99m pretty sure I searched for similar issues bef= ore posting, I missed it. Big thanks to Zsolt, Joao and Kirill for your input. I think combining work sounds like the reasonable thing to do. I=E2=80=99d b= e happy to help out in either thread. If any of you already know if one patch is preferable over the other, please= do tell. If not I=E2=80=99ll review and try posting a follow-up. I=E2=80=99ve slowly started to implement a =E2=80=9Cstart streaming directly= after slot creation=E2=80=9D-functionality and perhaps that could work with= either patch. //Jesper Sent from my iPhone > On 16 Nov 2026, at 13:09, Andrey Borodin wrote: > =EF=BB=BFHi Magnus, all, >=20 > Nick reported the same startpoint/slot race in August [0], tracked in > CF 7233 [1]. The client patch there opens the streaming connection and > creates its slot before BASE_BACKUP, but starts streaming only after > receiving the backup startpoint. Your proposal goes further than that. >=20 > We also discussed cleanup of a newly created permanent slot when > BASE_BACKUP refuses to start. Zsolt's reports of slot invalidation and > idle timeout are relevant to that approach too. >=20 > Could we combine the work and keep both threads linked from one CF > entry? This thread is currently tracked separately as CF 7613 [2]. >=20 > Thank you! >=20 > Best regards, Andrey Borodin. >=20 > [0] https://www.postgresql.org/message-id/CALP_NYTTvKzJ+chEUXLsyGaM+HYcP1W= wGwXkZEnDfv-7FbPowQ@mail.gmail.com > [1] https://commitfest.postgresql.org/patch/7233/ > [2] https://commitfest.postgresql.org/patch/7613/