View Issue Details

IDProjectCategoryView StatusLast Update
0011513Talermerchant backendpublic2026-06-12 14:35
Reportervecirex Assigned Tovecirex Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityurgentSeverityblockReproducibilityhave not tried
Status closedResolutionfixed 
Summary0011513: Check DB restore w/ backup from merchant v1.6.2; then upgrade to merchant v1.6.4
DescriptionAn issue introduced in taler-merchant v1.6.3 rel to Garbage Collection, was tested to make instances inaccessible: should be fixed in taler-merchant v1.6.4; testing herewith.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

child of 0011511 closedvecirex Taler Test global KYC Auth Reset for an installation's instances and in taler-merchant v1.6.4 

Activities

vecirex

2026-06-11 18:21

administrator   ~0028867

Last edited: 2026-06-11 19:09

Steps for restore (radical, but clean approach: only suited if the system's psql installation solely used for taler-merchant; nothing else; restore file to be a backup file from pg_dumpall):

SQL_RESTORE_FILE=/root/backups/postgres-backup-1781051251.sql
systemctl stop postgresql
systemctl stop taler-merchant.target
ps -axw | grep taler # only grep itself to be catched; if
pg_dropcluster 17 main --stop # using postgresql v17
pg_createcluster 17 main
systemctl start postgresql
sudo -u postgres psql --echo-all -f $SQL_RESTORE_FILE postgres # -> no errors
sudo -u postgres psql -l # taler-merchant DB should be visible, w/ user taler-merchant-httpd as user

vecirex

2026-06-12 14:35

administrator   ~0028874

Restore works fine; noticeable is that a minimal DB grows from around 4MB to 13MB (as of pg_dumpall sql dumps) due to the new (more clearly separated) schemes w/ every instance having its own: that is, things go from joins to iterations, as what concerns global views.

Issue History

Date ModifiedUsernameFieldChange
2026-06-11 16:25vecirexNew Issue
2026-06-11 16:26vecirexAssigned To => vecirex
2026-06-11 16:26vecirexStatusnew => assigned
2026-06-11 16:29vecirexRelationship addedchild of 0011511
2026-06-11 16:29vecirexRelationship replacedparent of 0011511
2026-06-11 16:30vecirexRelationship replacedchild of 0011511
2026-06-11 18:21vecirexNote Added: 0028867
2026-06-11 18:21vecirexNote Edited: 0028867
2026-06-11 18:22vecirexNote Edited: 0028867
2026-06-11 18:30vecirexNote Edited: 0028867
2026-06-11 19:09vecirexNote Edited: 0028867
2026-06-11 19:09vecirexNote Edited: 0028867
2026-06-12 14:35vecirexStatusassigned => closed
2026-06-12 14:35vecirexResolutionopen => fixed
2026-06-12 14:35vecirexNote Added: 0028874