Logical replication stalling for large tables with heavy write activity - Pg11

From: Mukesh Chhatani <chhatani(dot)mukesh(at)gmail(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Logical replication stalling for large tables with heavy write activity - Pg11
Date: 2020-08-15 22:17:44
Message-ID: CACnmOY+bERRrHDATkWqLQaL9g4rFu0SStinkNJSrRcThg8tNnA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello Team,

I am working on upgrading Postgres at my current organization using logical
replication.

In most of the cases Logical replication works fine, but in below scenario
it just stalls for more than 24 hours

Primary DB - Pg10.11
Table Size - 90 GB including 20 GB of indexes

Secondary - Pg11.6

After few hours table is still being copied in the pg_stat_replication and
plg_replication_slot I can replication is live currently and table size on
the secondary is increasing,

When I check the table size on the primary using
pg_size_pretty(pg_total_relation_size('test')), it shows 90 GB but on the
secondary where replication is happening it shows more than 150GB, and
still replication is in progress with no errors in the logs.

This problem does not happen with tables which have less write activity
(updates/inserts).

Please let me know if this is a known issue or is there any way I can fix
this problem using some configuration.

Any insights would be gratefully appreciated.

Thanks & Regards,
Mukesh Chhatani

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-08-17 12:02:41 BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails
Previous Message Peter Geoghegan 2020-08-14 21:32:57 Re: BUG #16582: Logical index corruption leading to apparent index scan infinite loop