Skip to content

fix(postgres): use 2000-01-01 epoch for standby status update timestamp - #2538

Open
ryder777777 wants to merge 1 commit into
getdozer:mainfrom
ryder777777:fix/postgres-standby-status-epoch-2352
Open

ryder777777 wants to merge 1 commit into
getdozer:mainfrom
ryder777777:fix/postgres-standby-status-epoch-2352

Conversation

@ryder777777

Copy link
Copy Markdown

Summary

  • Updates the PostgreSQL logical replication standby status update (PrimaryKeepAlive reply) in dozer-ingestion/postgres/src/replicator.rs to compute elapsed time since the PostgreSQL epoch (2000-01-01 00:00:00 UTC) instead of 2020-01-01 00:00:00 UTC.
  • Extracts standby_status_timestamp and adds unit test coverage verifying the 2000-01-01 00:00:00 UTC epoch calculation.

Closes #2352

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The wrong timestamp is being used in the postgres replication protocol

1 participant