@peter_kosztolanyi Hello, I am using Transferwise tap & target to sync pg2pg with LOG_BASED as replication method. I have run the

meltano elt tap-postgres target-postgres

quite a few times sucessfully, but for each table I get the following:

Beginning sync of stream(public-xxxxxxxx) with sync method(logical_initial)
Performing initial full table sync

And it does updates instead of inserts

{"inserts": 0, "updates": 100000, "size_bytes": 11064744}

but the data is the same It doesn’t seem to be reading from the replication log, but it seems it always does a full refresh. Am I doing something wrong? My source database is AWS Aurora Postgres 11.9 with rds.logical_replication set to 1 in the Parameter Group

👋 unfortunately I’m not too familiar using tap-pg with meltano :<

so, if I was to run the tap directly, I should get different results?

yes, you need to have

wal2json

plugin configured and you also need to create replication slot

Ok, I am using RDS Aurora, but have managed. Does the naming of the replication_slot matter?

SELECT *
  FROM pg_create_logical_replication_slot('pipelinewise_<database_name>', 'wal2json');

If my source database is named

fevo

, does this need to be named

pipelinewise_fevo

? (equal to the

dbname

in the tap)

@dejan_pejcev Creating

pipelinewise_<dbname>

did the trick, right?

that is definitely a requirement

Yep, let's document that more clearly or link to the GitHub readme instead of just the doc on the pipelinewise website

Hey @douwe_maan, I know it's an old thread but I have a question if we have any replication slot naming requirements for the Meltano (default) tap-postgres?