challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE

commit 5c4dd7599cb7fa7f4814fd51a39d6bd62078c06a
parent 158b559c6f46f8bc693bd6a95b0cd3d2bbc48afa
Author: Christian Grothoff <christian@grothoff.org>
Date:   Mon,  6 Jul 2026 10:43:22 +0200

keep serializable on both paths

Diffstat:
Msrc/challengerdb/pg.c | 4++++
1 file changed, 4 insertions(+), 0 deletions(-)

diff --git a/src/challengerdb/pg.c b/src/challengerdb/pg.c @@ -64,6 +64,10 @@ reconnect_cb (struct CHALLENGERDB_PostgresContext *pg, }; #else struct GNUNET_PQ_ExecuteStatement es[] = { + /* https://wiki.postgresql.org/wiki/Serializable suggests to really + force the default to 'serializable' if SSI is to be used. */ + GNUNET_PQ_make_try_execute ( + "SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL SERIALIZABLE;"), GNUNET_PQ_make_execute ("SET search_path TO challenger;"), GNUNET_PQ_EXECUTE_STATEMENT_END };