use table locks to prevent stale reads from trigger (MRXN23-572)

Vizzuality · Jan 31, 2024 · c7c1eb0 · c7c1eb0
1 parent 5bf5056
commit c7c1eb0
Showing 1 changed file with 7 additions and 0 deletions.
diff --git a/api/apps/geoprocessing/src/import/pieces-importers/scenario-metadata.piece-importer.ts b/api/apps/geoprocessing/src/import/pieces-importers/scenario-metadata.piece-importer.ts
@@ -124,6 +124,13 @@ export class ScenarioMetadataPieceImporter implements ImportPieceProcessor {
         if (scenarioCloning) {
           await this.updateScenario(em, scenarioId, metadata, input.ownerId);
         } else {
+          /**
+            * Aggressive locking on the table is used here in order to ensure that by the time
+            * the trigger function that is executed on insert will not get stale data from
+            * concurrent transactions. Inserting in serializable mode seems not to be enough,
+            * from checks done when this lock was added.
+            */
+          await em.query('lock table scenarios');
           await this.createScenario(
             em,
             scenarioId,