How to use the Postgre XMIN Connector.

Postgres is one of the popular and widely used SQL databases. It also now supports JSON payloads as well as can be used as a data warehouse with the right configuration. The MovingLake Postgres XMIN connector uses the internal logic for Multiversion Concurrency Control to check for latest data changes in a batched manner.

Keep into account that XMIN version replication does not propagate deletes.

If the destination is a SQL-like database, data is upserted using the primary key(s) of the source database. If a source table has no primary keys, then information is appended into the destination table.

Connector guide.

Create a user with read permissions

If you are using RDS, be sure to do this with a user with sufficent privileges. Remember to change the user and password with whatever you choose.

If your tables are in a schema other than public, be sure to change that as well.

-- Create a read only group  
CREATE ROLE readaccess;  
  
-- Grant access to existing tables  
GRANT USAGE ON SCHEMA public TO readaccess;  
GRANT SELECT ON ALL TABLES IN SCHEMA public TO readaccess;  
  
-- Grant access to future tables  
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO readaccess;  
  
-- Create a final user with password  
CREATE USER movinglake WITH PASSWORD 'secret';  
GRANT readaccess TO movinglake;

Entities supported with this connector.

By the default only a virtual entity is supported, dbstate. Ensure to enter a valid cron expression.

Important: all cron expressions are treated as UTC time.