RE: Logical Replication of sequences
Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: Add documentation for sequence synchronization.
- 55cefadde874 19 (unreleased) landed
-
Remove unused assignment in CREATE PUBLICATION grammar.
- bfb7419b0bbe 19 (unreleased) landed
-
Add seq_sync_error_count to subscription statistics.
- f6a4c498dcf6 19 (unreleased) landed
-
Fix few issues in commit 5509055d69.
- 5a4eba558aa7 19 (unreleased) landed
-
Add sequence synchronization for logical replication.
- 5509055d6956 19 (unreleased) landed
-
Add worker type argument to logical replication worker functions.
- 3e8e05596a02 19 (unreleased) landed
-
Introduce "REFRESH SEQUENCES" for subscriptions.
- f0b3573c3aac 19 (unreleased) landed
-
Refactor logical worker synchronization code into a separate file.
- 41c674d2e31e 19 (unreleased) landed
-
Standardize use of REFRESH PUBLICATION in code and messages.
- 2436b8c047ff 19 (unreleased) landed
-
Add "ALL SEQUENCES" support to publications.
- 96b378497346 19 (unreleased) landed
-
Expose sequence page LSN via pg_get_sequence_data.
- b93172ca59f4 19 (unreleased) landed
-
Resume conflict-relevant data retention automatically.
- 0d48d393d465 19 (unreleased) cited
-
Post-commit review fixes for 228c370868.
- 1f7e9ba3ac4e 19 (unreleased) cited
-
Generate GUC tables from .dat file
- 63599896545c 19 (unreleased) cited
On Monday, October 13, 2025 3:00 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Sat, Oct 11, 2025 at 7:42 PM vignesh C <vignesh21@gmail.com> wrote: > > > > The attached patch has the changes for the same. > > > > 5. > AlterSubscription_refresh() > - sub_remove_rels[remove_rel_len].relid = relid; > - sub_remove_rels[remove_rel_len++].state = state; > … > - char originname[NAMEDATALEN]; > + SubRemoveRels *rel = palloc(sizeof(SubRemoveRels)); > + > + rel->relid = relid; > + rel->state = state; > + > + sub_remove_rels = lappend(sub_remove_rels, rel); > > Why do we change an offset based array into list? It looks slightly > odd that in the same function one of the other similar array > pubrel_local_oids is not converted when the above is converted. And > even if we do so, I don't think we need a retail free > (list_free_deep(sub_remove_rels);) as the memory allocation here is in > portal context which should be reset by end of the current statement > execution. when sub_remove_rels was Array type, we used subrel_count as the initial size of this array, but this count means the number of both the table and sequences. So it allocates some unnecessary space for it, which is why we changed it to List. Based on above, I kept the current style for now but removed the list_free. All other comments have been addressed in the latest version. Best Regards, Hou zj