On Tue, Jul 5, 2022 at 11:05 AM Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:
On 7/5/22 10:56 AM, shashidhar Reddy wrote:
> Down time 10 to 15 hrs
> Hardware specs are also not sure for now as it is client machine.
This is going to be a difficult task for the following reasons:
In other words there is going to be a lot of preliminary work and
testing that is going to need to be done before you even start the
transfer. The first of that is determining what your setup is. My guess
is you will end up doing this in stages of using intervening Postgres
versions.
I would seriously try and make this work by performing, even if not entirely consistent, a dump of the minimal subset of the database needed to meet most of the day-to-day needs of the applications using the database. Create a v13 (or whatever supported version you want really) database schema from scratch (dump schema only restore or whatever you've got in version/migration control). Load the data into it and make sure that everything is working properly. Then, resync the newest stuff and go live while incurring additional downtime for migrating the likely decade plus of historical data that is out there probably generally unused. Setting up partitions, or maybe even some separate archival database to be linked into the new one via Foreign Data Wrappers, can also be considered.
David J.
