fix: avoid postgres migration version collision

This commit is contained in:
fawney19
2026-05-29 16:18:59 +08:00
parent 91a5e58cec
commit 92ae88f1be
3 changed files with 4 additions and 2 deletions
@@ -7,7 +7,7 @@ use tracing::info;
// Generated by build.rs from schema/bootstrap/postgres.
pub(crate) static EMPTY_DATABASE_SNAPSHOT_SQL: &str =
include_str!(concat!(env!("OUT_DIR"), "/empty_database_snapshot.sql"));
pub(crate) const EMPTY_DATABASE_SNAPSHOT_CUTOFF_VERSION: i64 = 20260528000000;
pub(crate) const EMPTY_DATABASE_SNAPSHOT_CUTOFF_VERSION: i64 = 20260528010000;
const PUBLIC_BASE_TABLE_COUNT_SQL: &str = r#"
SELECT COUNT(*)::BIGINT
@@ -319,6 +319,7 @@ fn empty_database_snapshot_covers_current_cutoff_versions() {
20260524000000,
20260527000000,
20260528000000,
20260528010000,
]
);
}
@@ -343,7 +344,7 @@ fn empty_database_snapshot_includes_tables_created_by_stamped_migrations() {
fn routing_profiles_repair_migration_creates_missing_tables() {
let migration = POSTGRES_MIGRATOR
.iter()
.find(|migration| migration.version == 20260528000000)
.find(|migration| migration.version == 20260528010000)
.expect("routing profiles repair migration should be embedded");
assert!(migration
@@ -1555,6 +1556,7 @@ fn pending_migrations_from_applied_skips_versions_already_applied() {
20260524000000,
20260527000000,
20260528000000,
20260528010000,
]
);
}