From 85f7813d758f75810c22d887b52ff4e01f297812 Mon Sep 17 00:00:00 2001 From: dakkar Date: Fri, 20 Jun 2025 14:01:17 +0100 Subject: [PATCH] use a *very* long statement_timeout for migrations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit some migrations still timeout with the ×10, let's hope that ×100 is enough! (if people have not set a timeout in the configuration files, this commit changes the migration timeout from 1m40s to 16m40s) --- packages/backend/ormconfig.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/backend/ormconfig.js b/packages/backend/ormconfig.js index c88b3b3d65..62c8fe36fc 100644 --- a/packages/backend/ormconfig.js +++ b/packages/backend/ormconfig.js @@ -14,7 +14,7 @@ export default new DataSource({ extra: { ...config.db.extra, // migrations may be very slow, give them longer to run (that 10*1000 comes from postgres.ts) - statement_timeout: (config.db.extra?.statement_timeout ?? 1000 * 10) * 10, + statement_timeout: (config.db.extra?.statement_timeout ?? 1000 * 10) * 100, }, entities: entities, migrations: ['migration/*.js'],