[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-sync] branch master updated: remove locking, we'll revert to sequ
From: |
gnunet |
Subject: |
[taler-sync] branch master updated: remove locking, we'll revert to sequential use as locking requires superuser |
Date: |
Wed, 06 Sep 2023 21:27:25 +0200 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository sync.
The following commit(s) were added to refs/heads/master by this push:
new f294b27 remove locking, we'll revert to sequential use as locking
requires superuser
f294b27 is described below
commit f294b27630de8e4621e049907b94d52ab2b3eb79
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Wed Sep 6 21:27:21 2023 +0200
remove locking, we'll revert to sequential use as locking requires superuser
---
src/syncdb/versioning.sql | 4 ----
1 file changed, 4 deletions(-)
diff --git a/src/syncdb/versioning.sql b/src/syncdb/versioning.sql
index c7fa812..444cf95 100644
--- a/src/syncdb/versioning.sql
+++ b/src/syncdb/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.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-sync] branch master updated: remove locking, we'll revert to sequential use as locking requires superuser,
gnunet <=