pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jesper St John <admin@zonezero.se>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Zsolt Parragi <zsolt.parragi@percona.com>
Cc: Jesper St John <jesper@stjohn.se>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Cc: Kirill Reshke <reshkekirill@gmail.com>
Subject: Re: Timing issue in pg_basebackup
Date: Tue, 17 Nov 2026 12:35:37 +0100
Message-ID: <4F71E8F4-32D9-4B37-9DA9-203564F00692@zonezero.se> (raw)
In-Reply-To: <4E8EC951-B75E-4CB8-97B6-D5C21F88A991@yandex-team.ru>
References: <4E8EC951-B75E-4CB8-97B6-D5C21F88A991@yandex-team.ru>

Hi!

Sorry, even though I’m pretty sure I searched for similar issues before 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’d be 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’ll review and try posting a follow-up.

I’ve slowly started to implement a “start streaming directly after slot creation”-functionality and perhaps that could work with either patch.

//Jesper


Sent from my iPhone

> On 16 Nov 2026, at 13:09, Andrey Borodin <x4mmm@yandex-team.ru> wrote:
> Hi Magnus, all,
> 
> 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.
> 
> 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.
> 
> Could we combine the work and keep both threads linked from one CF
> entry? This thread is currently tracked separately as CF 7613 [2].
> 
> Thank you!
> 
> Best regards, Andrey Borodin.
> 
> [0] https://www.postgresql.org/message-id/CALP_NYTTvKzJ+chEUXLsyGaM+HYcP1WwGwXkZEnDfv-7FbPowQ@mail.gmail...
> [1] https://commitfest.postgresql.org/patch/7233/
> [2] https://commitfest.postgresql.org/patch/7613/






view thread (11+ messages)

Message-ID: <4F71E8F4-32D9-4B37-9DA9-203564F00692@zonezero.se>
Permalink:  ../4F71E8F4-32D9-4B37-9DA9-203564F00692@zonezero.se/
Also on:    postgresql.org/message-id/4F71E8F4-32D9-4B37-9DA9-203564F00692@zonezero.se

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: admin@zonezero.se, x4mmm@yandex-team.ru, magnus@hagander.net, zsolt.parragi@percona.com, jesper@stjohn.se, reshkekirill@gmail.com
  Subject: Re: Timing issue in pg_basebackup
  In-Reply-To: <4F71E8F4-32D9-4B37-9DA9-203564F00692@zonezero.se>
  References: <4E8EC951-B75E-4CB8-97B6-D5C21F88A991@yandex-team.ru> <4F71E8F4-32D9-4B37-9DA9-203564F00692@zonezero.se>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox