A clone created using a custom time zone is not deleted after the timeout (maxIdleMinutes)
Goal
A clone created using a custom time zone is not deleted after the timeout (maxIdleMinutes)
maxIdleMinutes: 2
- Create a clone with the custom timezone (Europe/Stockholm)
root@vitaliy-dle-test:~# dblab clone create --username test_user --password test-pass --id clone_01 --extra-config log_timezone='Europe/Stockholm'
{
"id": "clone_01",
"protected": false,
"deleteAt": null,
"createdAt": "2023-04-27T18:58:47Z",
"status": {
"code": "OK",
"message": "Clone is ready to accept Postgres connections."
},
"db": {
"connStr": "host=localhost port=6001 user=test_user dbname=postgres",
"host": "localhost",
"port": "6001",
"username": "test_user",
"password": "",
"dbName": ""
},
"snapshot": {
"id": "dblab_pool/dataset_1@snapshot_20230427185109",
"createdAt": "2023-04-27T18:53:22Z",
"dataStateAt": "2023-04-27T18:51:09Z",
"pool": "dblab_pool/dataset_1",
"numClones": 1,
"physicalSize": "0 B",
"logicalSize": "617 MiB"
},
"metadata": {
"cloningTime": 1.547954935,
"maxIdleMinutes": 120,
"cloneDiffSize": "261 KiB",
"logicalSize": "617 MiB"
}
}
root@vitaliy-dle-test:~# psql "host=localhost port=6001 user=test_user dbname=postgres"
Password for user test_user:
psql (15.2 (Ubuntu 15.2-1.pgdg22.04+1))
Type "help" for help.
postgres=# show log_timezone;
log_timezone
------------------
Europe/Stockholm
(1 row)
- Create a new clone with default timezone (UTC)
root@vitaliy-dle-test:~# psql "host=localhost port=6000 user=test dbname=postgres" -c "show log_timezone"
Password for user test:
log_timezone
--------------
Etc/UTC
(1 row)
- clone_01 -
log_timezone='Europe/Stockholm'
- clone_02 -
log_timezone='Etc/UTC'
Then:
- clone_02 with 'Etc/UTC' was deleted
- clone_01 with 'Europe/Stockholm' NOT deleted
TODO / How to implement
Acceptance criteria
clone is deleted by the timeout (maxIdleMinutes
)