Tolu Aina

Thanks for this. I am keep to learn from what you did to optimise the query path.

yes this is a known issue. I will address this together with [this](https://github.com/toluaina/pgsync/issues/296) issue as there are slightly related

pgsync relies on the `triggers` and `pg_notify` for the bulk of routine operations. `txid_current` is used as a checkpoint and this does not wrap around However the internal xids attached...

Did you re-run bootstrap command after changing the schema.json? Also delete any checkpoint files starting with a dot

Are you absolutely sure about this? Also can you confirm you re-ran bootstrap after changing the schema. i.e adding a new index/database pair. I am unable to reproduce this .

@divit00 I don't think this is correct. Each entry/node in the schema.json is unique and identified by its database name and index name. We index documents at the database level,...

PGSync does not sync individual tables. Its syncs a collection of tables in a database. The schema.json only supports checkpoints at the database combined with the index. This is used...

pgsync is supposed to work across database schemas. So this is supporting a functionality. That said there is probably a more efficient way of skipping non-relevant tables.

This is not supported yet. It was also requested [here](https://github.com/toluaina/pgsync/issues/290). I am still working on this

- I'm afraid this was not solved in the new release. - Its a bit delicate which is why it wasn't done to start with. - I have started working...