Re: Resetting recovery target parameters in pg_createsubscriber

2025-09-16 Thread Alyona Vinter
rring to? Or do you mean all the descriptive comments? For context, I'm currently working on the version where my patch is being tested in CI. I will work on improving the code and will also add the documentation notes that Michael has pointed out ASAP. Best regards, Alyona Vinter

Re: Timeline switching with partial WAL records can break replica recovery

2025-09-10 Thread Alyona Vinter
ished on the target. This ensures we always begin from a known-valid position in WAL. I'd appreciate any feedback! Best Regards, Alyona Vinter From 8cf7ed6aa3de1984f3512ec13bfdfab32e36364c Mon Sep 17 00:00:00 2001 From: Alena Vinter Date: Mon, 26 May 2025 13:18:35 +0700 Subject: [PATCH 1/3]

Re: Resetting recovery target parameters in pg_createsubscriber

2025-09-07 Thread Alyona Vinter
Sorry, wrong patches again. Here are the correct ones. Best regards, Alyona Vinter From baed4d6390737c4274cd4dc1c21d7bf488c673d4 Mon Sep 17 00:00:00 2001 From: Alena Vinter Date: Tue, 2 Sep 2025 18:15:13 +0700 Subject: [PATCH 2/2] Implements helper function in recovery_gen These functions

Re: Resetting recovery target parameters in pg_createsubscriber

2025-09-07 Thread Alyona Vinter
Hi, CFbot indicated some issues with the patch. I've attached rebased versions of the patches, so hopefully everything will be ok this time. Best regards, Alyona Vinter On Fri, 5 Sept 2025 at 12:51, Alyona Vinter wrote: > Dear Hayato, > > Thank you for the review! My apologies

Re: Resetting recovery target parameters in pg_createsubscriber

2025-09-04 Thread Alyona Vinter
Dear Hayato, Thank you for the review! My apologies for the error in the patch -- it looks like I accidentally modified it before sending =(. I've attached the fixed versions below. > Regarding patch content, your patch restores the postgresql.auto.conf after the > command runs. Initially I felt

Re: Timeline switching with partial WAL records can break replica recovery

2025-09-02 Thread Alyona Vinter
s lost and the cascade replica is promoted (as described above), the downstream replica may enter an infinite loop during recovery instead of properly following the new timeline. -- Regards, Alyona Vinter > From 6dd413c17424d91ccb3f9df8a95d37ef905c555a Mon Sep 17 00:00:00 2001 From: Alena Vint

Re: Timeline switching with partial WAL records can break replica recovery

2025-09-02 Thread Alyona Vinter
On Wed, 3 Sept 2025 at 12:37, Alyona Vinter wrote: > I've found an error in my previous patch and have attached a fixed version. > Sorry, I've sent the wrong patches again. Here the correct ones From c947c47c95c625520f2eef2183e1f42594bf0c83 Mon Sep 17 00:00:00 2001 From: Alena V

Re: Resetting recovery target parameters in pg_createsubscriber

2025-09-02 Thread Alyona Vinter
; code. I kept primary_conninfo as-is for now since I'm not totally sure if we need to touch it I look forward to your feedback! ;) Best regards, Alyona Vinter From 94ca21fd0b3e683c4b03b552a3c7baa7f376eed3 Mon Sep 17 00:00:00 2001 From: Alena Vinter Date: Tue, 2 Sep 2025 18:15:13 +0700 Subject: [PATCH 1/

Re: Making WAL archiving faster — multi-file support and async ideas

2025-08-26 Thread Alyona Vinter
ished. If Postgres detects that the segment isn't in the archive yet, it simply waits for it to appear. Let me know if I’ve missed anything here. Then I see no fundamental problem with the parallel archiver =) Best wishes, Alyona Vinter

Re: Making WAL archiving faster — multi-file support and async ideas

2025-08-25 Thread Alyona Vinter
paradigm. Given that the archiver already uses a priority queue, this should not be difficult to implement. Thanks for considering my feedback. -- Best regards, Alyona Vinter On Mon, 25 Aug 2025 at 11:00, Stepan Neretin wrote: > Hi hackers, > > We’ve been thinking about how to