On Wed, Oct 8, 2025 at 9:13 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Tue, Oct 7, 2025 at 5:46 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
>
> > > I have one more question: while testing the sequence sync, I found
> > > this behavior is documented as well[1], but what's the reasoning
> > > behind it? Why REFRESH PUBLICATION will synchronize only newly added
> > > sequences and need to use REFRESH PUBLICATION SEQUENCES to
> > > re-synchronize all sequences.
> > >
> >
> > The idea is that REFRESH PUBLICATION should behave similarly for
> > tables and sequences. This means that this command is primarily used
> > to add/remove tables/sequences and copy their respective initial
> > contents. The new command REFRESH PUBLICATION SEQUENCES is to sync the
> > existing sequences, it shouldn't add any new sequences, now, if it is
> > too confusing we can discuss having a different syntax for it.
>
> Sure, let's discuss this when we get this patch at the start of the
> commit queue.
>
I have pushed the publications related patch. Now, we can discuss this
command. I think confusion arises from the fact that both commands use
REFRESH. So, how about for the second case (sync/copy all existing
sequences), we use a different command, some ideas that come to my
mind are:
Alter Subscription sub1 REPLICATE Publication Sequences;
Alter Subscription sub1 RESYNC Publication Sequences;
Alter Subscription sub1 SYNC Publication Sequences;
Alter Subscription sub1 MERGE Publication Sequences;
Among these, the first three require a new keyword to be introduced. I
prefer to use existing keyword if possible. Any ideas?
--
With Regards,
Amit Kapila.
