[libeufin] branch master updated: remove locking, we'll revert to sequential use as locking requires superuser

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository libeufin.

The following commit(s) were added to refs/heads/master by this push:
     new 105256d6 remove locking, we'll revert to sequential use as locking 
requires superuser
105256d6 is described below

commit 105256d62189fdbbbbc2e8026edcdb225afbe534
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Wed Sep 6 21:28:51 2023 +0200

    remove locking, we'll revert to sequential use as locking requires superuser
---
 database-versioning/new/versioning.sql | 4 ----
 database-versioning/versioning.sql     | 4 ----
 2 files changed, 8 deletions(-)

diff --git a/database-versioning/new/versioning.sql 
b/database-versioning/new/versioning.sql
index c7fa8121..444cf95e 100644
--- a/database-versioning/new/versioning.sql
+++ b/database-versioning/new/versioning.sql
@@ -146,10 +146,6 @@
 
 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.
diff --git a/database-versioning/versioning.sql 
b/database-versioning/versioning.sql
index c7fa8121..444cf95e 100644
--- a/database-versioning/versioning.sql
+++ b/database-versioning/versioning.sql
@@ -146,10 +146,6 @@
 
 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.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.