Does anybody know why

pipelinewise-tap-postgres

cannot get messages from the wal log with logical replication? It just echoes

Waiting for first wal message

but I see a couple of logs above it says

Request wal streaming from 0/FE7F90B8 to 0/FF49E768 (slot pipelinewise_xxxxxxx)

I've responded on https://meltano.slack.com/archives/C013EKWA2Q1/p1616516707110100

initially it was working, for 2-3 days, and stopped all of a sudden :

@dejan_pejcev Weird. You may want to try https://github.com/singer-io/tap-postgres instead, but

pipelinewise-tap-postgres

was based on that one, and they both use logical replication in the same way: • https://github.com/transferwise/pipelinewise-tap-postgres/blob/master/tap_postgres/sync_strategies/logical_replication.py#L609 • https://github.com/singer-io/tap-postgres/blob/master/tap_postgres/sync_strategies/logical_replication.py#L435

meaning my apps should take care of the

updated_at

?

yeah, key-based replication will only pick up updates if it has a way to tell if a row got updated since the last sync

the tap detects everything correctly. It sees it needs to use the

pipelinewise_xxxxx

(database name instead of xxxxx) should be used, it sees that it should stream wal records from LSN X to LSN Y, but receives nul when psycopg2 tries to read from the log

Right. I'm sure that that tap is running in production with log-based replication in various places, so I wonder if there's something off about your postgres server

hmmm I’m using AWS RDS Aurora Postgres v12.4

Hmm, no reason to think that wouldn't be configured perfectly then

@dejan_pejcev finding a similar issue with

tap-postgres

. Were you able to find a solution for this?