Mimeo can be used to move database tables from one PostgreSQL database to another.
Includes support for three replication strategies:
1. Snapshot - entire table copied from one DB to another
2. Incremental - data is moved as new content is detected
3. DML - takes data from one database and permanently moves it to a new location
· PostgreSQL 9.1 or higher
· pg_jobmon 0.3 or higher
· PostgreSQL dblink extension
What's New in This Release: [ read full changelog ]
· Logdel refresh function now has a "repull" option to do a complete refresh of data from the source. Note that it will NOT delete the rows on the destination that were previously deleted from the source (only deletes rows on the destination where mimeo_source_deleted column is null). Since a TRUNCATE cannot be done as is done with the other replication repulls, it is highly recommended to do a manual VACUUM of destination table after this is done, possibly even a VACUUM FULL to reclaim disk space.
· To help the above repull process be more efficient, an index is now created on the "mimeo_source_deleted" destination column of all newly created logdel replication tables. Existing replication tables will not have this index added. Recommend adding one if you need to do this repull method on old setups.
· DML & Logdel replication source queue tables now have indexes created on the "processed" and "processed, mimeo_source_deleted" columns respectively. This should help replication be more efficient for higher traffic tables that create larger queues. Existing replication sets will not have their source queue table modified to add this index. Recommend going back and manually adding it if you notice performance problems.
· Exception messages if dml/logdel maker functions fail are clearer about what has happened reguarding objects created on the source.
· Added p_debug option to maker functions. Also made debugging a little cleaner and have it provide more information in many cases.
· Bug Fix: WHERE condition of logdel replication wasn't working properly.