 |
| ||||
Mimeo can be employed to go database tables from one particular PostgreSQL databases to a different.
Involves help for a few replication approaches :
one. Snapshot - overall desk copied from one DB to yet another
2. Incremental - knowledge is moved as new articles is detected
3. DML - normally takes facts from one particular databases and permanently moves it to a new site
Necessities :
· PostgreSQL 9. one or larger
· pg_jobmon. 3 or higher
· PostgreSQL dblink extension
What is New in This Release : [ examine total changelog ]
· New refresh_ table selection for just undertaking a straight truncate and repull for a normal desk. Only incorporating as a small attribute since other modifications do not affect API and it really is not suggested as a common refresh career if attainable. Also refresh_ desk () does not currently log to pg_jobmon, so can't be monitored and will not set off any alerts if/when this refresh variety fails. What this is beneficial for is acquiring a way to get info from production to a staging/dev database exactly where you nonetheless want to be in a position to edit the vacation spot table. Could do that with Incremental or DML, but this avoids demanding any primary keys, management columns or create accessibility on the source database.
· Taken off personalized enum form. Created items significantly a lot more difficult than they wanted to be. Enums are Really negative in extensions because you can by no means just add a new worth in an update.
· The commands to eliminate the batch restrict defaults & established the default boundaries for incremental replication had been missing from the mimeo--. nine. three --. ten. 1 bypass update file. If that file was used to update mimeo, the defaults ended up under no circumstances changed and boundaries were however becoming set for new refresh jobs. Run individuals below yet again.
Via: Mimeo 0.10.3
No comments:
Post a Comment