Hacker News Reader

How does it work in the event of real time changes happening on the database(s)?

It appears not to use logical decoding/replication. If so, how it does sync the data? It sounds like a hard problem, and not very efficient, to do it without logical decoding/replication.

I didn't see documentation about it. Unless.. it is intended to be used only with offline databases.

View on HN

It's batch sync, not streaming or replication. By default, appears to dedupe based on PK.

Is this two-way or one-way sync? It's sounding like it's one-way. I don't see anything about how to deal with clobbers, for instance, if the same data is changed in two different databases at the same time.

And "batch one-way sync" is better described as "copy".

So I think this is a "postgres database copy" tool. Also known as clone, or backup. And as such, it's competing with the existing postgres database cloning tools, like pg_dump. So how is this different than that?

One-way, yes. pg's COPY command can't do upserts, this can.

The primary use case for this appears to be ETL. Pg_dump is more backup-oriented and optimized for larger operations, vs. a bit more fine-grained in most ETL processes.

Kind of like MSSQL SSIS, but with only data export-import functionality.

Reply on news.ycombinator.com