| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Jesper St John <jesper(at)stjohn(dot)se>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Kirill Reshke <reshkekirill(at)gmail(dot)com> |
| Subject: | Re: Timing issue in pg_basebackup |
| Date: | 2026-11-16 12:08:50 |
| Message-ID: | 4E8EC951-B75E-4CB8-97B6-D5C21F88A991@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.com
[1] https://commitfest.postgresql.org/patch/7233/
[2] https://commitfest.postgresql.org/patch/7613/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nisha Moond | 2026-11-16 12:19:26 | Re: BUG #19892: Logical replication skips UPDATE/DELETE of rows with NULL in a hash-indexed subscriber column |
| Previous Message | Tor Erik Linnerud | 2026-11-16 11:26:36 | PG 18 JIT regression: int4range hash breaks multi-key GROUP BY |