Jean Weeber

I'm having a similar issue, though in my case a `company` instance isn't available as a fixture at all. Only `CompanyFactory` is registered as `company_factory`.

We are having the exact same issue, 35,075,199 records sync over successfully initially, but the automated sync does not work afterwards. The logs look exactly the same as that of...

@tthanh @jinserk Could either of you post the PGSync JSON schema that was used?

Yes I have, all indices are present.

Though this fix does reduce the disk usage, though I'm not sure if the `upto_nchanges` parameter of `PG_LOGICAL_SLOT_PEEK_CHANGES` is working as you expect. This query returns numerous results: ``` SELECT...

Hi @toluaina, Sorry for the delay, I've tested but I'm still having issues with this. I believe the problem might be with versions of Postgres < `14.0` - I have...

> work_mem has the default value (4MB). @rere16 As mentioned by @toluaina, try to increase your server's `work_mem`. Even though it's the default, 4MB is quite low for modern hardware....

To add to the above; if your schema name changed, pgsync will attempt to create a new replication slot with the new name whilst the old slot still exists. If...

@AnkitKundariya When you drop a replication slot, Postgres will remove the WAL logs and new transactions will no longer be 'recorded'. Therefor, there's no way for pgsync to 'replay' those...

@joshuafernandes1996 Your key is named `settings` and should be named `setting`.