Hi Dirk,
Yes, this will work fine. You can use the existing backup to restore it on
the new node and use the WAL archives from new node for the recovery
purpose. As a best practice, I would suggest setting the parameter
"recovery_target_timeline=latest" in your recovery command to ensure the
recov
Hi,
If the requirement is to take online backup(hot) backup that can be used to
do point in time recovery, you can rely on low-level API functionality
mentioned earlier by Paul. If you to be care free about not missing any
specific mount point other than default mount point, you can use
pg_basebac
the existing cluster before you start with the upgrade.
initialize the new cluster
initdb -D *$PGDATA12*
and then
./pg_upgrade -b $OLD/bin -B $NEW/bin -d $PG_DATA -D *$PGDATA12* -k -c
Best Regards,
*Sushant Pawar | Database Solution Consultant*
*ASHNIK TECHNOLOGY SOLUTIONS PVT. LTD.*
Skype
Hi Mihalidesová,
It should work with -k option. Can you share the error that you have
received? You can execute pg_upgrade with -c option to identify any
possible manual change required.
Best Regards,
*Sushant Pawar | Database Solution Consultant*
*ASHNIK TECHNOLOGY SOLUTIONS PVT. LTD
