> On Apr 18, 2026, at 18:28, James Pang <[email protected]> wrote:
>
> experts:
> source database v14 , pglogical extension 2.4.5 replication to new 17,
> source table very frequent UPDATEs /DELETES /INSERTS and has two text and
> jsonb. in source database, application update/delete/insert through SQL,
> table size did not increased quickly. but in target pg v17 , by pglogical
> apply, we found table increased very quickly , table size got doubled in
> days.
> Vacuum analyze did not help , only vacuum full can help. pgstattuple show
> most of space are free space , that much more than source. it looks like
> these replicate DML always asking new pages instead of reuse existing
> freespace.
> Thanks,
>
> James
Hello,
1. First, are you *sure* that the free space is the source of the bloat, and
not dead tuples? Could you share the queries you ran to detrmine this?
2. Have you set fillfactor to anything besides 100 on either the source or the
destination?
3. You might consider using in-core logical replication rather than pglogical
for this. By PostgreSQL v14, in-core logical replication is likely a better
choice.
Best,
-- Christophe
