v5.5.1: Critical native engine fixes
All checks were successful
CI/CD / Test (push) Successful in 3m3s
CI/CD / Lint (push) Successful in 1m9s
CI/CD / Integration Tests (push) Successful in 51s
CI/CD / Native Engine Tests (push) Successful in 50s
CI/CD / Build Binary (push) Successful in 44s
CI/CD / Test Release Build (push) Successful in 1m19s
CI/CD / Release Binaries (push) Successful in 11m5s
All checks were successful
CI/CD / Test (push) Successful in 3m3s
CI/CD / Lint (push) Successful in 1m9s
CI/CD / Integration Tests (push) Successful in 51s
CI/CD / Native Engine Tests (push) Successful in 50s
CI/CD / Build Binary (push) Successful in 44s
CI/CD / Test Release Build (push) Successful in 1m19s
CI/CD / Release Binaries (push) Successful in 11m5s
Fixed: - Native restore now connects to target database correctly (was connecting to source) - Sequences now properly exported (fixed type mismatch in information_schema query) - COPY FROM stdin protocol now properly handled using pgx CopyFrom - Tool verification skipped when --native flag is used - Fixed slice bounds panic on short SQL statements Changes: - internal/engine/native/manager.go: Create engine with target database for restore - internal/engine/native/postgresql.go: COPY handling, sequence type casting - cmd/restore.go: Skip VerifyTools in native mode - internal/tui/restore_preview.go: Native engine mode bypass Tested: 100k row backup/restore cycle verified working
This commit is contained in: