yida-db-seq-fix

PostgreSQL primary key conflicts occur after data migration when sequences fall behind the maximum existing ID values, causing new inserts to generate duplicate keys instead of continuing from the correct auto-increment position.

To fix PostgreSQL sequence start values, run a dry-run preview to detect inconsistencies across core tables, then execute the repair command to patch sequences to max(id)+1 and verify the corrected results safely.

A dry-run preview for database sequence auto-correction is a mandatory safety check that displays the impact range of adjusting sequence starts to max(id)+1 before applying any changes, preventing unintended data modifications.

Yes, you need an active PostgreSQL connection with access to the target database to detect current sequence values, compare them against maximum IDs in core tables, and execute the required sequence start value patches.

Sequence value auto-correction targets core tables including form_component, form_definition, form_instance, form_permission, process_definition, process_instance, process_task, and system_log to ensure consistent primary key generation.

Yes, you can trace and audit PostgreSQL sequence fixes because the repair process logs all operations during the correction workflow, providing full traceability for tracking sequence adjustments and problem resolution.