Arunprasad Rajkumar
Arunprasad Rajkumar
@shusaan Could you please try clone with `--no-owner`?
@shusaan We don't have ETA yet. I think, the first good to step is getting https://github.com/dimitri/pgcopydb/pull/312 merged into master. It is on my TODO list. Next step would be making...
I'm not sure the default behavior of `pgcopydb snapshot --follow` is useful. When we run second time, it skips creating replication slot which is fine, but prints the snapshot-id which...
I think implementing a proper undo log will become tricky to unless we resort to a transactional file write. Maybe opening the latest file and appending a ROLLBACK(if last txn...
> > I think implementing a proper undo log will become tricky to unless we resort to a transactional file write. Maybe opening the latest file and appending a ROLLBACK(if...
@dimitri , I believe truncating the table on startup would be simple. Let me attempt a fix. Thank you.
I think the main blocker would be that we create sentinel tables on the SOURCE., we may not able to do that if we connect to standby?
I think the PR https://github.com/dimitri/pgcopydb/pull/655 should close this issue.
@dimitri Do you think this could be merged to the main?
So far we have been evaluating pg_dump/pg_restore to (1)migrate schema (2)initial data and 3) `pgcopydb follow` with some custom changes(child table to parent mapping) for live message replication. I will...