relaynetwork/irmgard

Postgres Data Replication Framework

irmgard's Issues

Enhance irmgard.upsert_row_change to do an UPSERT

It currently just does an insert. Also add the functional indexes to ensure uniqueness of tracked rows.

Swap watcher's control ref for java.util.concurrent.AtomicBoolean

This should result in a minor reduction in overhead.

Convert observer-fn to take a seq

process-row-changes currently sends 1 record at a time into the observer-fn, when it selects a page of records from row_changes, it should group them by schema/table and hand those to the observer-fn's as a seq, allowing for smarter bulk operations.

process-row-changes: group records by schema/table

Implement the reduction to pass observer-fn a seq of records.

Irmgard should log an error if no listener is registered

Currently if row changes are identified, and there is no listener for the changes, Irmgard discards the records. It should also issue a log/error indicating the database, schema and table name for which it was unable to find a listener.

remove 'config' and other test helpers from main code

There are several helper functions in core.clj that are there to help with the example and test code. They should be removed before a first official release.

unregister should not throw an NPE

Currently it throws an NPE if the listener name is not registered (via calling name with nil).

Handle not getting the lock in irmgard clojure listener

Reconnect to Database If Connection Breaks

The watcher is not robust against its database connection breaking. Add a loop/recur and try/catch around the establishment of the connection before checking for changes.

Allow granting of permissions to service_user when irmgard is installed

service_user will need grants on irmgard schema/tables in order to actually use irmgard...

create helper function to install schema/tables and grant permissions to some user

implement tracking functions for text primary keys

Parallel the int primary key implementation.