From 66af1d2c14605ffd73a61cd02b947ca505c19eb5 Mon Sep 17 00:00:00 2001 From: Patrick DeVivo Date: Thu, 27 Oct 2022 09:57:28 -0400 Subject: [PATCH] fix: try back modifying the initial migration to make part of it idempotent (see if it addresses the error we see when running migrations using a different default pg user) --- migrations/20220511014018_init.up.sql | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/migrations/20220511014018_init.up.sql b/migrations/20220511014018_init.up.sql index 3d0bf7447..8839c3a3a 100644 --- a/migrations/20220511014018_init.up.sql +++ b/migrations/20220511014018_init.up.sql @@ -1,6 +1,6 @@ SET check_function_bodies = false; -CREATE EXTENSION pgcrypto; -CREATE SCHEMA mergestat; +CREATE EXTENSION IF NOT EXISTS pgcrypto; +CREATE SCHEMA IF NOT EXISTS mergestat; CREATE FUNCTION mergestat.set_current_timestamp_updated_at() RETURNS trigger LANGUAGE plpgsql AS $$