challenger

commit 986072be515341085a43dfd045c61be41408aa82
parent d72bec42356e986196b9abeeff8c5d6cae046dc4
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Sun, 27 Aug 2023 14:05:55 +0200

-fix issue with multiple dbinit running concurrently

Diffstat:
M
src/challengerdb/versioning.sql
 | 
7
++++++-

1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/src/challengerdb/versioning.sql b/src/challengerdb/versioning.sql
@@ -146,12 +146,17 @@
 
 BEGIN;
 
+-- Added by Christian Grothoff to support concurrency, see
+-- https://stackoverflow.com/questions/29900845/create-schema-if-not-exists-raises-duplicate-key-error?rq=4
+LOCK TABLE pg_catalog.pg_namespace;
+
+
 -- This file adds versioning support to database it will be loaded to.
 -- It requires that PL/pgSQL is already loaded - will raise exception otherwise.
 -- All versioning "stuff" (tables, functions) is in "_v" schema.
 
 -- All functions are defined as 'RETURNS SETOF INT4' to be able to make them to RETURN literally nothing (0 rows).
--- >> RETURNS VOID<< IS similar, but it still outputs "empty line" in psql when calling.
+-- >> RETURNS VOID<< IS similar, but it still outputs "empty line" in psql when calling
 CREATE SCHEMA IF NOT EXISTS _v;
 COMMENT ON SCHEMA _v IS 'Schema for versioning data and functionality.';