View Issue Details

IDProjectCategoryView StatusLast Update
0007890Talerlibeufin (general)public2023-09-23 15:09
ReporterMS Assigned ToMS  
PriorityurgentSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.9.3Fixed in Version0.9.3 
Summary0007890: DB connection string needs ordinary postgres:// format.
DescriptionAll libeufin expects DB connection strings to have the format starting with "jdbc".
This however makes difficult to pass such strings between libeufin and other components,
notably the shell script (libeufin-load-sql) that loads the SQL files into the database.

Another disadvantage is the passing of JDBC connection strings that rely on Unix domain
sockets, because these are not user friendly.

The solution is therefore to change all libeufin to accept postgres://-formatted connection
strings, instead of the JDBC ones.
TagsNo tags attached.

Activities

Christian Grothoff

2023-07-23 16:47

manager   ~0020359

I fully agree, that'll be much better! We should in fact stop using JDBC eventually, and thus certainly also jdbc:-uris.

MS

2023-07-24 11:20

reporter   ~0020368

Fixing this bug would help to avoid database permission issues, because there will
be always _one_ user going in the database. Right now, if the database is accessed
via TCP, _some_ operations happen under the current process user instead of the one
mentioned in the TCP connection string.

MS

2023-07-25 17:14

reporter   ~0020383

Addressed here: 54717e5c9630a5ed8bec955f06ba4e2359e20dfc

Now being tested.

MS

2023-07-28 16:59

reporter   ~0020385

Last edited: 2023-07-28 17:00

The new version fails when a connection string starts with "postgres:///" and accepts only "postgresql:///". It should be adapted to accept both formats.

MS

2023-07-28 17:15

reporter   ~0020386

That should be fixed in this version: 48c1cc4ce7e338d14093b2e04ccd621282a451ee

Documentation update is forthcoming.

Christian Grothoff

2023-08-28 12:49

manager   ~0020447

Yes, this seems to be fine now.

Issue History

Date Modified Username Field Change
2023-07-22 09:49 MS New Issue
2023-07-22 09:49 MS Status new => assigned
2023-07-22 09:49 MS Assigned To => MS
2023-07-22 09:50 MS Target Version => 0.9.4
2023-07-23 16:47 Christian Grothoff Note Added: 0020359
2023-07-24 11:12 MS Target Version 0.9.4 => 0.9.3
2023-07-24 11:20 MS Note Added: 0020368
2023-07-24 11:38 Christian Grothoff Priority normal => urgent
2023-07-24 11:38 Christian Grothoff Product Version => git (master)
2023-07-25 17:14 MS Status assigned => feedback
2023-07-25 17:14 MS Note Added: 0020383
2023-07-28 16:59 MS Note Added: 0020385
2023-07-28 17:00 MS Note Edited: 0020385
2023-07-28 17:15 MS Note Added: 0020386
2023-08-28 12:49 Christian Grothoff Status feedback => resolved
2023-08-28 12:49 Christian Grothoff Resolution open => fixed
2023-08-28 12:49 Christian Grothoff Fixed in Version => 0.9.3
2023-08-28 12:49 Christian Grothoff Note Added: 0020447
2023-09-23 15:09 Christian Grothoff Status resolved => closed