I’m using a PostgreSQL v17 database (running in Docker on a Synology NAS), and everything works fine. However, the problem arises when I backup the database and later restore it. The recovery process goes smoothly, and everything seems fine with the database.
However, when I add the restored database as an additional database in mAirList, the database ID remains the same as the original database.
This has never happened in previous iterations/versions—mAirList would always assign a new ID to the database automatically.
When cloning the database within mAirlist you can choose to keep or change the database ID.
As soon as you restore that backup, the database will be added with the new ID.
This way you can have 2 (possibly identical) databases work synchronously.
So you should not export the database but clone it.
Personally, I don’t know whether you can easily change the database ID afterwards
Thank you for providing the possible sollution, the thing is, im not talking about cloning the database in that way. Im using sort of server/nas cron dump database option (with or without compression). And the issue is as i said before, when i recover that backup database file as new database, the id od the database remains the same. Ive never experienced that sort of behaviour before.
Usually when i do the postgresql database backup via cronjob or pgadmin option, and later restore that backed db to use in mairlist, the mairlist itself generates the new id and therefore there are no id conflict issues.
