Feature add pgcrypto ext

[zhuliquan]

Sometime, we want to use external PG. However, However lower version PG (i.g. 12.16) may not support gen_random_uuid function by default and get following error in migration stage.

{"timestamp":"2024-11-27T10:22:03.165300Z","level":"ERROR","fields":{"message":"Failed to run migrations on PostgresConfig { database_name: \"postgres\", host: \"10.252.176.141\", port: 25432, user: \"postgres\", password: Sensitive(\"JvVQknYlPYhJe2.P_ZAa1\") }: Error { kind: Connection(\"error applying migration V6__add_cluster_table\", Error { kind: Db, cause: Some(DbError { severity: \"ERROR\", parsed_severity: Some(Error), code: SqlState(E42883), message: \"function gen_random_uuid() does not exist\", detail: None, hint: Some(\"No function matches the given name and argument types. You might need to add explicit type casts.\"), position: Some(Original(264)), where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some(\"parse_func.c\"), line: Some(631), routine: Some(\"ParseFuncOrColumn\") }) }), report: Some(Report { applied_migrations: [] }) }"},"target":"arroyo"}

Here, we must enable pgcrypto extension. So I add below SQL for this case.

CREATE EXTENSION IF NOT EXISTS pgcrypto;

[zhuliquan]

It's seems not compatiable with history migration

[mwylde]

This approach won't work unfortunately; migrations are hashed and that's used to determine which ones have been applied. So if we modify an existing migration that will break it for everyone who's already run them.

I think that instead we could run this on the database before invoking the migrations in main:

arroyo/crates/arroyo/src/main.rs

Line 375 in 29e96b0

let report = migrations::migrations::runner()

[zhuliquan]

yeah, I have fix it now.

[mwylde]

Thanks!