View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011511 | Taler | deployment and operations | public | 2026-06-11 11:04 | 2026-06-11 21:01 |
| Reporter | vecirex | Assigned To | vecirex | ||
| Priority | urgent | Severity | block | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Summary | 0011511: Test global KYC Auth Reset for an installation's instances and in taler-merchant v1.6.4 | ||||
| Description | Test extension to ticket 0011446. Text was: Just to be sure, as stage is now running taler-merchant v1.6.3 and has garbage collection of the psql DB ("taler-merchant") fixed; should not cause problems, but better test. Indeed, issues arised, so to be done first: Test GC to work properly in v1.6.4; cf. 0011513. Then (to the core of this ticket): It was not yet tested to delete the *.kyc_merchant data of all instances at once and then request an update form the exchange on this. | ||||
| Tags | No tags attached. | ||||
|
|
Other DB-related tests first needed, which are related to GC since taler-merchant v1.6.3. |
|
|
Cannot be tested in taler-merchant v1.6.3, will be tested in taler-merchant v1.6.4. |
|
|
From stage running taler-merchant v1.6.4, in sql w/ user postgres:taler-merchant=# SELECT format( 'DELETE FROM %I.merchant_kyc;', schema_name ) FROM information_schema.schemata WHERE schema_name LIKE 'merchant_instance_%'; DELETE FROM merchant_instance_23.merchant_kyc; DELETE FROM merchant_instance_22.merchant_kyc; DELETE FROM merchant_instance_21.merchant_kyc; DELETE FROM merchant_instance_19.merchant_kyc; DELETE FROM merchant_instance_25.merchant_kyc; DELETE FROM merchant_instance_17.merchant_kyc; DELETE FROM merchant_instance_20.merchant_kyc; DELETE FROM merchant_instance_16.merchant_kyc; DELETE FROM merchant_instance_15.merchant_kyc; DELETE FROM merchant_instance_14.merchant_kyc; DELETE FROM merchant_instance_24.merchant_kyc; DELETE FROM merchant_instance_12.merchant_kyc; DELETE FROM merchant_instance_11.merchant_kyc; DELETE FROM merchant_instance_10.merchant_kyc; DELETE FROM merchant_instance_9.merchant_kyc; DELETE FROM merchant_instance_8.merchant_kyc; DELETE FROM merchant_instance_7.merchant_kyc; DELETE FROM merchant_instance_6.merchant_kyc; DELETE FROM merchant_instance_18.merchant_kyc; DELETE FROM merchant_instance_5.merchant_kyc; DELETE FROM merchant_instance_4.merchant_kyc; DELETE FROM merchant_instance_3.merchant_kyc; DELETE FROM merchant_instance_2.merchant_kyc; DELETE FROM merchant_instance_1.merchant_kyc; (27 rows) (END) Loop for deletion of *.kyc_merchant could go like this (pure sql):
DO $$
DECLARE s text;
BEGIN
FOR s IN
SELECT schema_name
FROM information_schema.schemata
WHERE schema_name LIKE 'merchant_instance_%'
AND schema_name <> 'merchant_instances'
LOOP
RAISE NOTICE 'Deleting from: %.merchant_kyc', s;
EXECUTE format('DELETE FROM %I.merchant_kyc;', s);
END LOOP;
END $$;
Dry-run looks like this; on stage system:
taler-merchant=# DO $$
DECLARE s text;
BEGIN
FOR s IN
SELECT schema_name
FROM information_schema.schemata
WHERE schema_name LIKE 'merchant_instance_%'
AND schema_name <> 'merchant_instances'
LOOP
RAISE NOTICE 'Would delete from: %.merchant_kyc', s;
END LOOP;
END $$;
NOTICE: Would delete from: merchant_instance_27.merchant_kyc
NOTICE: Would delete from: merchant_instance_26.merchant_kyc
NOTICE: Would delete from: merchant_instance_23.merchant_kyc
NOTICE: Would delete from: merchant_instance_22.merchant_kyc
NOTICE: Would delete from: merchant_instance_21.merchant_kyc
NOTICE: Would delete from: merchant_instance_19.merchant_kyc
NOTICE: Would delete from: merchant_instance_25.merchant_kyc
NOTICE: Would delete from: merchant_instance_17.merchant_kyc
NOTICE: Would delete from: merchant_instance_20.merchant_kyc
NOTICE: Would delete from: merchant_instance_16.merchant_kyc
NOTICE: Would delete from: merchant_instance_15.merchant_kyc
NOTICE: Would delete from: merchant_instance_14.merchant_kyc
NOTICE: Would delete from: merchant_instance_24.merchant_kyc
NOTICE: Would delete from: merchant_instance_12.merchant_kyc
NOTICE: Would delete from: merchant_instance_11.merchant_kyc
NOTICE: Would delete from: merchant_instance_10.merchant_kyc
NOTICE: Would delete from: merchant_instance_9.merchant_kyc
NOTICE: Would delete from: merchant_instance_8.merchant_kyc
NOTICE: Would delete from: merchant_instance_7.merchant_kyc
NOTICE: Would delete from: merchant_instance_6.merchant_kyc
NOTICE: Would delete from: merchant_instance_18.merchant_kyc
NOTICE: Would delete from: merchant_instance_5.merchant_kyc
NOTICE: Would delete from: merchant_instance_4.merchant_kyc
NOTICE: Would delete from: merchant_instance_3.merchant_kyc
NOTICE: Would delete from: merchant_instance_2.merchant_kyc
NOTICE: Would delete from: merchant_instance_1.merchant_kyc
DO
taler-merchant=#
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-06-11 11:04 | vecirex | New Issue | |
| 2026-06-11 11:04 | vecirex | Status | new => assigned |
| 2026-06-11 11:04 | vecirex | Assigned To | => vecirex |
| 2026-06-11 12:05 | vecirex | Priority | immediate => urgent |
| 2026-06-11 12:05 | vecirex | Status | assigned => confirmed |
| 2026-06-11 12:05 | vecirex | Note Added: 0028858 | |
| 2026-06-11 18:28 | vecirex | Summary | Test global KYC Auth Reset for an installation's instances and in taler-merchant v1.6.3 => Test global KYC Auth Reset for an installation's instances and in taler-merchant v1.6.4 |
| 2026-06-11 18:28 | vecirex | Note Added: 0028863 | |
| 2026-06-11 18:28 | vecirex | Status | confirmed => assigned |
| 2026-06-11 18:29 | vecirex | Relationship added | parent of 0011513 |
| 2026-06-11 18:29 | vecirex | Relationship replaced | child of 0011513 |
| 2026-06-11 18:30 | vecirex | Relationship replaced | parent of 0011513 |
| 2026-06-11 18:39 | vecirex | Description Updated | |
| 2026-06-11 18:41 | vecirex | Description Updated | |
| 2026-06-11 18:42 | vecirex | Description Updated | |
| 2026-06-11 21:00 | vecirex | Note Added: 0028868 | |
| 2026-06-11 21:01 | vecirex | Note Edited: 0028868 |