> Running pg_dump in new server probably takes much more time since data > Postgres version 12 pg_dump probably cannot installed in old server > pg_dump binary from the new server(12) to dump the old server(9.1) > Best practice if you are going the dump/restore route is to use the > I want to create test transfer first, check applications work and after > test the upgrade before doing it on your production setup. > Before you do any of this I would check the Release Notes for the Shared_buffer=1GB setting is currently used in nf No other applications are running during database Turning fsync off during restore speed up it ? Are there some settings which can used to speed up restore process ? Will (I'm new to linux, this is not postgresql related question)Ĥ. How to create shell script which reads all files from /root/backup I have done some minor testing and havent found issues.ģ. Is it OK to restore from 9.1 backups or should I create backups using Is there some command, script or pgadmin GUI for this ?Ģ. pgAdmin allows only deletion roles one by one. Use Postgres 12 pg_restore with job count 4 to restore those 24ġ. Run edited role definitons script using pgadmin in new server to createĥ. Manually edit role definitions to delete role postgres since it exists inĤ. Use pgAdmin "backup globals" command to dump role definitions is oldģ. Use pg_dump 9.1 in old server to create 24. Server used also in access rights in databases.ġ. There are also some hundred of Postgresql login and group roles in old Mbit (not 100 Mbit as I wrote), it took 5 minutes to copy 37 GB). (internet connection between those server is fast, SSH copy speed was 800 Read from uncompressed form and dumping is time-consuming process. Running pg_dump in new server probably takes much more time since data is Postgres version 12 pg_dump probably cannot installed in old server (Debian >binary from the new server(12) to dump the old server(9.1) >Best practice if you are going the dump/restore route is to use the pg_dump I want to create test transfer first, check applications work and after that >upgrade before doing it on your production setup. backup files and use pg_restore or use pipe toĪdrian you do any of this I would check the Release Notes for the first > internet connection and fixed IP addresses. > Both server have ssh and root user, postgres port 5432 open, 100 MB Pg_dump binary from the new server(12) to dump the old server(9.1) Upgrade before doing it on your production setup.īest practice if you are going the dump/restore route is to use the > How to transfer those databases to new server ?īefore you do any of this I would check the Release Notes for the first > I installed new VPS server with Debian 10 and Postgres 12. > Every night backup copies are created using pg_dump to /root/backups VPS server has old Debian 6 Squeeze with Postgres 9.1
0 Comments
Leave a Reply. |