​You can permanently migrate the live instance to the current postgresql, that will mean that you don't need to fettle around in the backup routine.
https://staging.validation.linaro.org/static/docs/v2/debian.html#migrating-postgresql-versions

I saw that link. The tutorial is explaining how to upgrade Postgresql. I do not think it is addressing downgrades. May be I am wrong. I did not follow those instructions to avoid issues but may be I should give it a try.


The Linaro lab just use pg_dump to create backups

I am also creating backups with pg_dumps. The issue is not there. The issues comes when trying to restore the backup on another host. My current host is using Postgresql-10. The second host is using Postgresql-9.6 because Postgresql-10 is no longer available for the second host. Then, on the second host, I can't use pg_restore due to Postgresql compatibility issues.

One idea could be downgrading the Postgresql-10 on the first host to Postgresql-9.6 using  https://staging.validation.linaro.org/static/docs/v2/debian.html#migrating-postgresql-versions (hopping it works). Then the second host will be able to use pg_restore without compatibility issues.



regards,


On 13 June 2018 at 16:36, Neil Williams <neil.williams@linaro.org> wrote:
On Wed, 13 Jun 2018 at 15:27, Conrad Djedjebi <conrad.djedjebi@linaro.org> wrote:
Thank you Neil,

I am writing a bash script to handle backups of my LAVA Server.
I am following the recommendations available here : https://staging.validation.linaro.org/static/docs/v2/admin-backups.html

​You can permanently migrate the live instance to the current postgresql, that will mean that you don't need to fettle around in the backup routine.


The Linaro lab just use pg_dump to create backups.​

 

Due to some incompatibilities with Postgresql versions, I am obliged to drop lavaserver database and recreate lavaserver database before restoring the tables from my backup.
I can't use pg_restore due to incompatibilities with Postgresql versions. Postgresql-10 is no longer available for debian and the latest stable version of LAVA, LAVA 2018.4-1~bpo9+1, is based on Postgresql-9.6. When I set up LAVA in March 2018, Postgresql-10 was still available and I have been using that version. Now, to backup, I have to migrate the database from Postgresql-10 to Postgresql-9.6. pg_restore do not allow it.

https://packages.debian.org/sid/postgresql-10 - also available in buster.​

​You can quite happily run LAVA using buster if you want to migrate to postgresql-10​

 

So, I am dropping lavaserver database, recreating lavaserver database and pushing the tables from Postgresql-10 using psql -f instead of pg_restore. For that purpose, I need lavaserver's databse password in my bash script.

regards

On 13 June 2018 at 16:10, Neil Williams <neil.williams@linaro.org> wrote:
On Wed, 13 Jun 2018 at 15:06, Conrad Djedjebi <conrad.djedjebi@linaro.org> wrote:
Good morning everyone,

I would like to know if the default password for lavaserver database created in Postgresql is available somewhere in the default configuration files?

​It's in /etc/lava-server/instance.conf

Normally, this isn't useful because you also need the Django environment settings to do anything useful in the database.

The best way to interact with the database is using Python3:

$ sudo lava-server manage shell​

 

Also, Is there a way to find out the default password for lavaserver user in the host?

​The lavaserver user is created without a password. To change to that user, just use:

$ sudo su lavaserver​

​What are you trying to do?​

 

regards,
_______________________________________________
Lava-users mailing list
Lava-users@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lava-users


--