| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
| Cc: | Ajin Cherian <itsajin(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Support automatic sequence replication |
| Date: | 2026-02-18 04:48:49 |
| Message-ID: | CAA4eK1L6czEzG4mLNZSyjYC5nX0FMSjjk3csKuxPD3Ph5-7Yvw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 17, 2026 at 4:51 PM Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> wrote:
>
>
> How about retaining ALTER SUBSCRIPTION ... REFRESH SEQUENCES command?
>
Yes, Shveta and myself also advocated the same for the upgrade case.
> It can be useful in scenarios where automatic sequence replication
> cannot be enabled, for example, due to the max_worker_processes limit
> on the server preventing a new worker from being registered. Since
> increasing max_worker_processes requires a server restart, which the
> user may not want to perform immediately, this command would provide a
> way to manually synchronize the sequences.
>
Good point. I think we won't be able to launch sync workers even when
we reach max_logical_replication_workers limit. So, this is one more
reason to retain the REFRESH SEQUENCES command.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2026-02-18 05:02:34 | Re: index prefetching |
| Previous Message | Nisha Moond | 2026-02-18 04:39:03 | Re: pgstat include expansion |