Configure the maximal number of parallel data transfers and index creation workers for each migration.
The Migrator picks reasonable default values when a new migration is created:Data Tranfers: number of CPUs where the Migrator is hostedDatabase Workers: number of CPUs of the target database. Make sure to tune this parameter with the PostgreSQL configuration of max_worker_processes, max_parallel_workers, max_parallel_maintenance_workers
Enhance sidebar: show synonym meta-data as pop-up
Set/clear object type filter by selecting an
Object Typein the overview tab. Use theCTRLkey to filter for more than one database object type.
Add issue templates for asking questions.
- Empty connection check error message on
504 Gateway Time-Out - Broken GUI workflow in the Analyze step on
504 Gateway Time-Out - Error on migrating
REVERSEindexes: PostgreSQL does not have/need an equivalent feature - Opening a non-existent migration endlessly shows the loading animation
- Error on migrating sequences with negative
INCREMENT-START value cannot be greater than MAXVALUE - Migration controls (resume, continue, etc.) occasionally do not behave as expected
- Views depending on other views are not created in the correct order
- Spacing between the migration log time and level is jumping
- Incorrect name conflict detection for tables and triggers with the same identifier