On Wed, Aug 6, 2025 at 8:48 AM shveta malik wrote:
>
> On Wed, Aug 6, 2025 at 7:35 AM Ajin Cherian wrote:
> >
> > On Tue, Aug 5, 2025 at 4:22 PM Amit Kapila wrote:
> > >
> > > On Tue, Aug 5, 2025 at 9:28 AM shveta malik
> > > wrote:
> > > >
> > > > On Mon, Aug 4, 2025 at 3:41 PM Amit Kapila
On Wed, Aug 6, 2025 at 7:35 AM Ajin Cherian wrote:
>
> On Tue, Aug 5, 2025 at 4:22 PM Amit Kapila wrote:
> >
> > On Tue, Aug 5, 2025 at 9:28 AM shveta malik wrote:
> > >
> > > On Mon, Aug 4, 2025 at 3:41 PM Amit Kapila
> > > wrote:
> > > >
> > > > On Mon, Aug 4, 2025 at 12:19 PM shveta malik
On Tue, Aug 5, 2025 at 4:22 PM Amit Kapila wrote:
>
> On Tue, Aug 5, 2025 at 9:28 AM shveta malik wrote:
> >
> > On Mon, Aug 4, 2025 at 3:41 PM Amit Kapila wrote:
> > >
> > > On Mon, Aug 4, 2025 at 12:19 PM shveta malik
> > > wrote:
> >
> > If we want to avoid continuously syncing newly added
On Fri, Aug 1, 2025 at 4:32 PM shveta malik wrote:
>
>
> Thanks for the patch. I tested it, please find a few comments:
>
>
> 1)
> it hits an assert
> (slotsync_reread_config()-->Assert(sync_replication_slots)) when API
> is trying to sync and is in wait loop while in another session, I
> enable s
On Tue, Aug 5, 2025 at 9:28 AM shveta malik wrote:
>
> On Mon, Aug 4, 2025 at 3:41 PM Amit Kapila wrote:
> >
> > On Mon, Aug 4, 2025 at 12:19 PM shveta malik wrote:
>
> If we want to avoid continuously syncing newly added slots in later
> cycles and instead focus only on the ones that failed to
On Mon, Aug 4, 2025 at 3:41 PM Amit Kapila wrote:
>
> On Mon, Aug 4, 2025 at 12:19 PM shveta malik wrote:
> >
> > On Mon, Aug 4, 2025 at 11:31 AM Amit Kapila wrote:
> > >
> > > On Fri, Aug 1, 2025 at 2:50 PM shveta malik
> > > wrote:
> > > >
> > > > 5)
> > > > I tried a test where there were 4
On Mon, Aug 4, 2025 at 12:19 PM shveta malik wrote:
>
> On Mon, Aug 4, 2025 at 11:31 AM Amit Kapila wrote:
> >
> > On Fri, Aug 1, 2025 at 2:50 PM shveta malik wrote:
> > >
> > > 5)
> > > I tried a test where there were 4 slots on the publisher, where one
> > > was getting used while the others w
On Mon, Aug 4, 2025 at 11:31 AM Amit Kapila wrote:
>
> On Fri, Aug 1, 2025 at 2:50 PM shveta malik wrote:
> >
> > 5)
> > I tried a test where there were 4 slots on the publisher, where one
> > was getting used while the others were not. Initiated
> > pg_sync_replication_slots on standby. Forced u
On Fri, Aug 1, 2025 at 2:50 PM shveta malik wrote:
>
> 5)
> I tried a test where there were 4 slots on the publisher, where one
> was getting used while the others were not. Initiated
> pg_sync_replication_slots on standby. Forced unused slots to be
> invalidated by setting idle_replication_slot_t
On Fri, Aug 1, 2025 at 12:02 PM shveta malik wrote:
>
> On Thu, Jul 31, 2025 at 3:11 PM Ajin Cherian wrote:
> >
> >
> > Patch v3 attached.
> >
>
> Thanks for the patch. I tested it, please find a few comments:
>
>
> 1)
> it hits an assert
> (slotsync_reread_config()-->Assert(sync_replication_slot
On Thu, Jul 31, 2025 at 3:11 PM Ajin Cherian wrote:
>
>
> Patch v3 attached.
>
Thanks for the patch. I tested it, please find a few comments:
1)
it hits an assert
(slotsync_reread_config()-->Assert(sync_replication_slots)) when API
is trying to sync and is in wait loop while in another session,
On Thu, Jul 17, 2025 at 2:04 PM shveta malik wrote:
>
> On Wed, Jul 16, 2025 at 3:47 PM Ajin Cherian wrote:
> >
> > > I am not able to apply the patch to the latest head or even to a week
> > > back version. Can you please check and rebase?
> > >
> > > thanks
> > > Shveta
> >
> > Rebased.
> >
>
>
On Mon, Jul 21, 2025 at 10:08 AM shveta malik wrote:
>
> On Sat, Jul 19, 2025 at 5:10 PM Amit Kapila wrote:
> >
> > On Fri, Jul 18, 2025 at 11:31 AM Dilip Kumar wrote:
> > >
> > > On Fri, Jul 18, 2025 at 11:25 AM shveta malik
> > > wrote:
> > > >
> > > > Okay. I see your point. Yes, it was no
On Mon, Jul 21, 2025 at 10:08 AM shveta malik wrote:
>
> On Sat, Jul 19, 2025 at 5:10 PM Amit Kapila wrote:
> >
> > On Fri, Jul 18, 2025 at 11:31 AM Dilip Kumar wrote:
> > >
> > > On Fri, Jul 18, 2025 at 11:25 AM shveta malik
> > > wrote:
> > > >
> > > > Okay. I see your point. Yes, it was no
On Sat, Jul 19, 2025 at 5:10 PM Amit Kapila wrote:
>
> On Fri, Jul 18, 2025 at 11:31 AM Dilip Kumar wrote:
> >
> > On Fri, Jul 18, 2025 at 11:25 AM shveta malik
> > wrote:
> > >
> > > Okay. I see your point. Yes, it was non-blocking earlier but it was
> > > not giving ERROR, it was just dumpin
On Fri, Jul 18, 2025 at 11:31 AM Dilip Kumar wrote:
>
> On Fri, Jul 18, 2025 at 11:25 AM shveta malik wrote:
> >
> > Okay. I see your point. Yes, it was non-blocking earlier but it was
> > not giving ERROR, it was just dumping in logilfe that primary is
> > behind and thus slot-sync could not be
On Fri, Jul 18, 2025 at 11:25 AM shveta malik wrote:
>
> Okay. I see your point. Yes, it was non-blocking earlier but it was
> not giving ERROR, it was just dumping in logilfe that primary is
> behind and thus slot-sync could not be done.
>
> If we continue using the non-blocking mode, there’s a
On Fri, Jul 18, 2025 at 10:52 AM Dilip Kumar wrote:
>
> On Fri, Jul 18, 2025 at 10:45 AM shveta malik wrote:
> >
> > On Fri, Jul 18, 2025 at 10:14 AM Dilip Kumar wrote:
> > >
> > > On Thu, Jul 17, 2025 at 9:34 AM shveta malik
> > > wrote:
> > > >
> > > > On Wed, Jul 16, 2025 at 3:47 PM Ajin Ch
On Fri, Jul 18, 2025 at 10:45 AM shveta malik wrote:
>
> On Fri, Jul 18, 2025 at 10:14 AM Dilip Kumar wrote:
> >
> > On Thu, Jul 17, 2025 at 9:34 AM shveta malik wrote:
> > >
> > > On Wed, Jul 16, 2025 at 3:47 PM Ajin Cherian wrote:
> > > >
> > > > > I am not able to apply the patch to the late
On Fri, Jul 18, 2025 at 10:14 AM Dilip Kumar wrote:
>
> On Thu, Jul 17, 2025 at 9:34 AM shveta malik wrote:
> >
> > On Wed, Jul 16, 2025 at 3:47 PM Ajin Cherian wrote:
> > >
> > > > I am not able to apply the patch to the latest head or even to a week
> > > > back version. Can you please check a
On Thu, Jul 17, 2025 at 9:34 AM shveta malik wrote:
>
> On Wed, Jul 16, 2025 at 3:47 PM Ajin Cherian wrote:
> >
> > > I am not able to apply the patch to the latest head or even to a week
> > > back version. Can you please check and rebase?
> > >
> > > thanks
> > > Shveta
> >
> > Rebased.
> >
>
>
On Wed, Jul 16, 2025 at 3:47 PM Ajin Cherian wrote:
>
> > I am not able to apply the patch to the latest head or even to a week
> > back version. Can you please check and rebase?
> >
> > thanks
> > Shveta
>
> Rebased.
>
Thanks. Please find a few comments:
1)
/* Any slot with NULL in these field
> I am not able to apply the patch to the latest head or even to a week
> back version. Can you please check and rebase?
>
> thanks
> Shveta
Rebased.
Regards,
Ajin Cherian
Fujitsu Australia.
v2-0001-Improve-initial-slot-synchronization-in-pg_sync_r.patch
Description: Binary data
On Wed, Jul 16, 2025 at 3:00 PM Ajin Cherian wrote:
>
> On Wed, Jul 2, 2025 at 7:56 PM shveta malik wrote:
> >
> > Few comments:
> >
> > 1)
> > When the API is waiting for the primary to advance, standby fails to
> > handle promotion requests. Promotion fails:
> > ./pg_ctl -D ../../standbydb/ pro
On Wed, Jul 2, 2025 at 7:56 PM shveta malik wrote:
>
> Few comments:
>
> 1)
> When the API is waiting for the primary to advance, standby fails to
> handle promotion requests. Promotion fails:
> ./pg_ctl -D ../../standbydb/ promote -w
> waiting for server to promote.stopped waiting
Please find few more comments:
1)
In pg_sync_replication_slots() doc, we have this:
"Note that this function is primarily intended for testing and
debugging purposes and should be used with caution. Additionally, this
function cannot be executed if "
We can get rid of this info as well and
On Tue, Jun 24, 2025 at 4:11 PM Ajin Cherian wrote:
>
> Hello,
>
> Creating this thread for a POC based on discussions in thread [1].
> Hou-san had created this patch, and I just cleaned up some documents,
> did some testing and now sharing the patch here.
>
> In this patch, the pg_sync_replicatio
Sorry, I attached the wrong file. Attaching the correct file now.
regards,
Ajin Cerian
Fujitsu Australia
0001-Improve-initial-slot-synchronization-in-pg_sync_repl.patch
Description: Binary data
28 matches
Mail list logo
