Hi,
There should be another line in the log for why the logical replication
worker has stopped in the first place. Something like Primary Key or Unique
Constraint violation, timeout on WAL sender or receiver process, etc.
Unless you can provide that information I doubt someone will be able to
help here.

Check logs on your both publisher and subscriber, with this information you
should be able to find the solution.

Cheers,
Mateusz

czw., 6 lip 2023 o 14:34 Paula Berenguel <paulaberenguel...@gmail.com>
napisaƂ(a):

> Hi
> I am using logical replication to move an on premises database PG11 to a
> cloud based PG11 and experiencing constant restart of the replication.
>
> The replication does it again. The validation_entry started again:
>
> 2023-07-06 01:49:46.968 UTC-64a61dba.1ad8----LOG: 00000: logical
> replication table synchronization worker for subscription "subXXXX", table
> "ZZZYYY" has started
>
> 2023-07-04 21:10:36.478 UTC-64a48b93.961----LOG: 00000: logical
> replication table synchronization worker for subscription "subXXXX",
> table " ZZZYYY" has started
>
>
> Can someone help me to find a fix for this?
>
>
> Thanks
>
> Paula
>

Reply via email to